fatcargo

Is it possible to create a UI asset bundle and use it so KSP plugin can add new UI elements at run-time (maybe copy existing UI element and adding it into existing hierarchy) ? So far, none of the tutorials mention such a possibility. Asset bundles appear to be static constructs. In my case, i will need arbitrary number of labels and sliders in vertical scrollable list.

Crafts in orbits can have two things in common : they can be not yet loaded (ie can be seen from KSC tracking station) and "under the hood" vessels in orbit (under fast warp, no accelerations from atmosphere or engines) have their physics turned off. To me it sounds like issue with unloaded vessels.

B9 Proc Wings have flaps/ailerons and procedural tanks/SRBs seem not to have anything animated (i tried to look for gimballed engines but found nothing). What is more important : in SPH/VAB procedural parts change shape and size while editing, does AA capture these events ? Even stock parts with variant switching may pose a challenge (oh and by the way do TweakScaled parts work OK too ?). It was showcased how various part can be attached and animated on flaps surfaces B9 PWings popped into my mind. One other test : do RCS and RCSFX parts properly update their thrust vectors when moved into new positions ? Did'nt see it in yt video... Another possible issue is with Kerbal Foundries wheels/tracks : few KSP versions back (old KF before unity wheel collider breakdown) i had trouble with KF wheels mounted on IR parts. Back then, KF wheels would in flight scene assume direction/steering on vessel load and after deployment via IR they did not work properly. This time i hope AA deployed KF wheels should not suffer from this (now they have different direction/steering setup).

Got this from post on IR Next thread. You did not just save my life .. you saved everyone ! Lately i don't have much time for playing KSP (though i am trying to make finish a mod, old and long story...) but can anyone test for compatibility with procedural mods like b9 proc wings and/or procedural parts (tanks ands SRBs) ?

I've tried also with alternate PlayerConnectionConfigFile generated on my system (which is kind of paradox since locally generated file is actually original, but i'm splitting hairs here ) and no luck. I then renamed my KSP debug player to "Unity.exe" (and added .pdb file from same editor install location where i copied debug player), made new link to folder and it (again) worked without a hitch. When i was googling around i found some post over on unity forums that unity debugger for VS needed to find "Unity.exe" process. Ehhh i guess this works too. If both debug player and editor are run at the same time, you can tell the difference because editor will have project name in list of debug listeners, ksp debug player will have that entry empty. Finally, if above does not work you can resort to listing all processes in system that have open listen ports (two TCP and one UDP, usually the second TCP is one you should connect to). Then open VS unity debugger and choose "Input IP" and enter 127.0.0.1:PORT. Problem is (at least on my machine) that every time ksp debug player is run, PORT number changes Oh and word of caution : i just noticed that VS unity debugger sees KSP debug player as "Editor". I don't know if it matters, but i tried inserting a breakpoint and it seems to work.

I then stand corrected. Thanks for reply ! I was lucky (and spent lots of time on it) to find out why is my install so finicky

UPDATE: i managed to make desired (minimal size) installation just for plugin development. First i used this to download required packages : vs_Community.exe --layout c:\vs2017offline --passive --wait --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Microsoft.Net.Component.3.5.DeveloperTools --add Microsoft.Net.Component.4.7.1.TargetingPack --add Microsoft.VisualStudio.Component.NuGet --add Microsoft.VisualStudio.Component.Roslyn.Compiler --add Microsoft.VisualStudio.Component.Roslyn.LanguageServices --add Microsoft.VisualStudio.Component.Static.Analysis.Tools --add Microsoft.VisualStudio.Component.Unity Above will load everything EXCEPT Unity3D package, i downloaded it separately. Command line will cause IDE to show so download progress will be visible. To install (similar command line) , run : PUSHD C:\vs2017offline vs_setup.exe --passive --norestart --wait --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Microsoft.Net.Component.3.5.DeveloperTools --add Microsoft.Net.Component.4.7.1.TargetingPack --add Microsoft.VisualStudio.Component.NuGet --add Microsoft.VisualStudio.Component.Roslyn.Compiler --add Microsoft.VisualStudio.Component.Roslyn.LanguageServices --add Microsoft.VisualStudio.Component.Static.Analysis.Tools --add Microsoft.VisualStudio.Component.Unity POPD Note that Unity3D package can be included entirely (shortening the "--add" packages command line) to just two entries. Also, above install command line supresses reboot, it may be needed to reboot after installing.

Debugging update on Windows for : KSP 1.4.3 build 2152 Unity3D 2017.1.3p1 Visual Studio 2017 v15 Original Instructions are mostly OK except for : - debug version of Unity player needs to be named "Unity.exe" (see notes below) - mklink command now needs to be "mklink /J Unity_Data KSP_x64_Data" (case insensitive, see notes below) [NOTES] If debug player is not named "Unity.exe", unity addon will not recognize it and will present empty "Select Unity Instance" window, offering network debugging via "Input IP" option where it needs both IP address and PORT. For IP address its simple, if VS debugger and game are on same machine but, there will be problem with PORT since (at least in my case) debug player changes port with each game run. Debug player is looking for Data folder named as "NameOfEXE_Data". [/NOTES] Note also that because KSP 1.4.x now runs on new version of Unity3D, old debugger addons no longer work (at least in my case, your expirience may differ) for example Xamarin or older VS2015. ... and yes yes i know i necropost, but to me this is "official" thread about debugging, and this is where i first got a working debug. I felt it needed updating. Paging dr. @sarbian please as time permits to update OP. Thanks in advance !

It's been quite a while (almost a year) since i last did some coding in KSP. To cut the story short : i tried searching and it didn't help. I guess my case is a little specific. When i start my VS 2017 Community and look at offered project templates, there is no "Class Library (.NET Framework)" i need to make a plugin. Note that my VS 2017 install is running purely from OFFLINE installer created using vs_community.exe as so : vs_community.exe --layout c:\vs2017offline --add [one.of.many.packages] Note that i used multiple --add command line arguments and that running the above does download packages. What i'm having issue with is that i can't guess which package(s) will cause IDE to show "Class Library (.NET Framework)" template. If i load old project (which i want to avoid using as "template") i can edit project preferences and i can see "class library" option. If i choose "blank project" template, project preferences are not available. Online/download from IDE is not an option since i want to save on network usage on any subsequent reinstalls, so i want a single download of all required packages and then actual install on target machine. Note also that due to KSP being switched to Unity 2017 and me needing to have debugging facilities (Tools for Unity VS2017 package) forced me to abandon VS2015 (which did not suffer from the above problem). References: Create and offline installation folder @ MS Visual Studio Community 2017 component directory @ MS, i used this in conjuction with UI for selecting workloads and then to figure out what packages i need (so far i did not see option to create local copy of packages from UI as i can with command line). Currently, i'm trying to download whatever is missing from VS installer UI, hoping to identify missing packages...

Oh and one more thing ... I don't know if this was reported before : when pulling extremely heavy payloads, craft tends to go all wonky and Kraken messes it up. I made a "submarine" (to be precise a Bathysphere) that uses IW-50 winch attached to four USI floats and USI Otter impeller . Main lander can that houses a scientist and scientific instrumentation are linked below winch. Negative buoyancy is achieved using Jatwaa's MOIST!UWT mod (added intake and a fuel tank at very bottom). Problem is that UWT mod introduces CompressedLiquid resource which is VERY heavy and only a tiny amount is required. If not careful, one can easily add 100 tonnes in no time at all. Lowering the pod is not a problem, but as soon as i tried to raise it, Kraken messed up the platform and bugged the winch, freezing it at about 20m of cable length claiming it can't retract because of blockage. I started with a probe core and build from there. Build was kind of in reverse because the manned lander can is attached to winch. I did this since i needed to maintain view focus on the pod, not the platform. Anyway the pics

I've created a new github issue for two more-less minor enhacements : 1. Adding "stop" action hroup for winches (haven;t found any in SPH/VAB) 2. Adding winch part with centered cable for vertically mass-aligned payloads

Feature request (or separate plugin) : manually bind craft to particular contract ? If there is such feature or plugin please direct me to it. Quite often i have multiple long term DMOS missions and i guess trying to sort them is part of "mission management experience" so i also ask if this makes sense or not. Currently, i name my crafts with agency/body/instrumentation/orbit parameters and then manually match them against contract list in CapCom.

And a side note for future reference : i just remembered the Sequencer for IR. It is ok as it is, but it got me wondering : would it be possible to create IR-driven compound part (basically a pre-built assembly) that contains Sequencer cfg ? Such part would be pre-programmed and built either by a part creator or player. Individual IR-parts would not be accessible in-game, only the whole assembly and only with predefined Sequencer input controls. This, combined with IR parts non-collision should allow for mechanically believable assemblies. Does any of this appeal (or even makes sense) to anyone ?

@jrodriguez Being the one to update B9 for 1.4.2 (big thanks !), i'm asking if this plugin supports anything with more complex geometry than planar surfaces like boxes, tubes or hollow spaces enclosed with multiple colliders ? The UI B9 Pwings offers is something i've never seen in any other plugin, so at least i'm willing to learn more about it before spending time making models.

thanks for pointing out the direction helper, now if only "turn" indicator would get added too ... Though i have to stress that doing "global" control via KF toolbar icon (stock/blizzy/etc...) would be better. Activate, look at wheels, tweak, turn off. One button to run them all A side note : is there a modeling tut for KF wheels/tracks ? Something with vanilla models in fbx that i can import and and have a look at ?

Feature request : Would it be possible to simulate direction and drive of KF wheels while still in SPH/VAB editor ? Some kind of "simulate" button that activates all wheels in editor (if not stowed, with slowed down drive rotation so player sees if direction is ok). Similar to Infernal Robotics Servo Control. That way player can see how wheels / tracks turn, so tweaking wheels does not become editor - flight - editor - flight-... testing we have now.

Feature request : i usually setup my experiments to run at once from action groups. As per usual, window for collected ALL data pops up offering the usual options + DMOS xmit so i can list and act on all of them. So far so good. However, once this window is closed, i can only either transmit all science (which available battery storage may not allow for) or select each science part and select "review" option to send data specifically for that experiment. So in short : @DMagic , can you add option to open AGAIN this data review window that lists ALL experiments ? It could be available as part menu option on any of science parts. Aaand i just realized it could be a separate plugin.

Thanks for the useful info ! RE point 2 : i was thinking along the lines of having custom motion parts that do not require rewriting IR. That way alternate complex/unusual joint groups can be added.

I wasn't sure to put my forward my ideas or not but here it goes ... 1. Concerning joints : it is possible to put multiple joints to a single part, let unity simulate them as per usual and where "outer" joints are the only ones with part's attachment nodes ? 2. To build on previous question : is it possible to make new IR have part configs that can let "aftermarket" users (such as @ZodiusInfuser ) write custom parts that have internally complex mechanics. Examples are helical motion drivers, spiral motion drivers, gearboxes (with one or multiple outputs). Math equations describing such motions may need to go into custom DLL modules (part.cfg may be insufficient) which is loaded by "master DLL" IR itself. 3. Would removing a joint (using Destroy() on it's component) make part connection between IR parts make them as rigid as any other "normal" part ? Would parts translated/rotated with that joint stay at those positions after destroying joint ? This would be presented as "fix" or "freeze" function to player. IR constructs would be unusable until player "reactivates" them but would be much more strong/rigid (even KJR may be notified about state of those parts and do it's magic on them, or not). I see this as the only way to have them as rigid as possible (i dabbled myself in C# trying to make simple robotic parts and noticed joints are the only way to go). This would make possible to have IR constructs not wobble too much during surface transports or launches.

Thanks for the effort and a kind response ! I had kind of rushed my post and forgot to add personally most crucial question of all : will this bridge let me write code and re-test it without restarting KSP ? If the above works as i assumed, then the workflow would go like this : 1. run unity editor, load unity-side of bridge 2.run ksp, load ksp-side of bridge as plugin (in my case as PartModule) 3. connect bridge, unity sends sources into KSP plugin code to be executed. code in KSP runs 4. run Visual Studio (or other C# IDE), open project 5. edit sources, change code as needed (squash bugs, add new features etc.. ) 6. unity detects file changes in project and sends them over bridge into KSP to run again This whole thing would let me write code in IDE that is aware of KSP's API (added references to DLLs) and test it near-instantly in KSP. So... how much did i assumed wrong ? If this works, it would be next to best possible option of actually HAVING sources for KSP itself as unity project.

Concerning Memory Mapped Files : i'm interested in using this "development system", but to me, this isn't well enough explained. Is it a plugin ? Or is this a piece of source code inserted into normal plugin code ? Does it need debug version of Unity3D player ? Where is a download link to a project/plugin for testing/development ? Are there any plans to document this ? Is KSP 1.4.x supported yet ?

Code fix was pushed to USI Tools module. When airbags were first moved from survivability pack to exploration it caught me by surprise so i learned the proper place for them actually i was lost when i first tried the github PR and was given directions . Here it is Please report back how it went. Hmmm... maybe a notice about deprecated parts can be put along with link to USI page ? At least newcomers would see a proper detour sign

@Jason-JT I can confirm that DLL was not compiled with updated sources. I've retrieved the sources from github and compiled them. Changes in code did fix airbag behavior. Are you willing to try my fixed DLL ?

I've seen the post earlier but didn't have enough time to explore it. After some minor "detective" work, i found that my pull request was approved, its source is present and it is listed as closed PR, as of August 10th . The compiled DLL in release folder containing the air bags module bears the write/upload date October 9th. This is 2 months time difference. The fix should be there. Either there is something broken (again, updates to KSP can mess up the addons) or DLL was never compiled from updated/fixed source (which would mean that fixed source was never synchronized back to machine which compiled the DLL). I'll try and see what went wrong. UPDATE : after finding time to do a test i confirmed that exploration pack from github still has the same Dampen() bug on horizontally launched/moving craft. In test, large airbags cut speed on my test plane just above 50 m/s. If this issue persists, i'll compile and upload it to somewhere. Oh and one more oddity : MKS, USI-LS etc are under UmbraSpaceIndustries github page, but ExpPack is under BobPalmer. Same person, but different "organizations" as github calls them. Not very beginner-friendly. Ah one more thing : I just noticed that issue ticket for this Dampen() bug is posted in USI github repository, but the actual part using this code/module is located under Exploration Pack. This kind of "dependency spread" can really make bug tracking difficult for the repository maintainers, i'd suggest moving KSP repos from BobPalmer to UmbraSpaceIndustries. Bug is present in module available on one page, but the part manifesting it is located on the other page, this can confuse everyone involved.

Thanks ! Will play around with this before implementing.