HarvesteR

It ocurred to me that there is little to no documentation at this point about the new ScenarioModules and how to add them to your game. With that in mind, I've written this brief guide as to how they are used. I'm assuming you already have some experience writing PartModules, in which case it should be relatively straightforward to learn how ScenarioModules operate. If not, I strongly suggest reading through the available PartModule coding tutorials and (admittedly very incomplete) documentation first. Let's get started then: Scenario Modules, just like PartModules, are compiled into dlls that go in the Plugins folder. In fact, nothing stops you from having ScenarioModules sharing dlls with PartModules. The dlls in Plugins simply add their classes to the game assembly. Once added, a ScenarioModule is loaded into the game through SFS files. In very much the same way you set up a PartModule in a part.cfg, you set up a ScenarioModule in an .sfs file: GAME { version = 0.17.0 Title = Orbiting 101 Description = This training scenario covers the basics of flying a blablabla.... // mode 0: Sandbox - mode 1: Career (not available yet), mode 2: Scenario, mode 3: Non-Resumable Scenario Mode = 3 // scene to load when starting this save. scene = 7 PARAMETERS { // flight parameter stuff } FLIGHTSTATE { // flight state data (in 0.16 this was your entire sfs file) } SCENARIO { // the name of the ScenarioModule class to spawn name = TutorialOrbit101 // the scene in which the module gets spawned (7 = flight) scene = 7 } } The only limitation at the moment is that to add a scenario module to your ongoing sandbox game, you'll need to manually add the module config to your persistent.sfs. Once added, it gets loaded into the persistence data structure and will remain in your sfs file even as it gets resaved and rewritten. ScenarioModules have one main difference from PartModules though. Because they are made to run on any scene, you must specify a target scene in which your module will run. Currently, modules can only run on one scene at a time. When a scene starts, the scenario module runner attaches all ScenarioModules that target that scene as a MonoBehaviour on an empty game object in the scene. You can use all MonoBehaviour events (except Awake), and code it in very much the same way you code part modules... Of course, there is no reference to vessel or part, since the module isn't attached to one. Hope this helps. Cheers

People have asked for it, so I thought it would be a good idea to promote this post I made a while back into a forum article. Hooray for VB! When I was little, I used to build model balsa-wood airplanes, and I learned some useful rules of thumb that might be worth sharing: One, if it looks like a plane, it will probably fly like a plane. Try a very conventional design before you go for the successor to the SR-71. The KRJ-100. Looks very much like a plane. It will glide without input. Two, the center of mass should be at the first third of the wings. Mentally divide your wing into three sections. The plane should be balanced at the first division threshold. (landing gear can be just aft of that, to provide a nice fulcrum) The KRJ-400 JetLiner, it\'s as heavy as it looks like. Three, vertical stabilizers should actually be pushing down, not up. Use the rotation feature in the SPH to pitch your elevators down a notch or two before placing. The wings alone will make the plane pitch down, while the stabilizers keep the nose up. Planes are stable when those forces even out. The Annihilator Mk1, the V tail acts as both rudder and elevator, and they\'re pitched down 10 degrees. Four, canards are like pushing on a rope. See rule 1. The Ravenspear Mk1 is much trickier to fly than the Annihilator. Pitch too aggressively, and it will tumble out of control. That\'s about it for now, hope this helps. Cheers