I agree. Consider that you'll have available the full set of possible features but each vessels only uses a subset of them. For example the ISS won't probably use the airfoils and the touchdownpoints sections, but will exploit at maximum the multimesh possibilities, while a spaceplane like the DG will probably use just one mesh but will try to exploit the airfoils at its best and so on.
Project VesselBuilder for Orbiter
- Thread starter fred18
- Start date
I agree. Consider that you'll have available the full set of possible features but each vessels only uses a subset of them. For example the ISS won't probably use the airfoils and the touchdownpoints sections, but will exploit at maximum the multimesh possibilities, while a spaceplane like the DG will probably use just one mesh but will try to exploit the airfoils at its best and so on.
I took a bit of time to fix and put a definitive seal to the Thrusters part.
I added the possibility to add an infinite number of custom pos and dir exhausts and particles, basically adding the only thing that was left out. The good part is that the user will define everything within the same thruster window, so very easy and intuitive: you define a thruster, then expand the window and define its exhausts and particle streams.
Here's the window not expanded
and here's the window expanded
I added the possibility to add an infinite number of custom pos and dir exhausts and particles, basically adding the only thing that was left out. The good part is that the user will define everything within the same thruster window, so very easy and intuitive: you define a thruster, then expand the window and define its exhausts and particle streams.
Here's the window not expanded
and here's the window expanded
the pre release is coming real soon. I want to add the variable drag elements which should be really easy and quick and then make a couple of fixes relevant to general stuff, like folders, configs etc. I will do my best to put out the prerelease within this weekend... I'm not promising but I'm confident. It will surely have some bugs here and there but at least users will start to get familiar with this.
And once the pre-release is out I will start working on the events that will make this much funnier also from the developing side!
Peculiar: after all this work now it became quite boring to define the length of an exhaust or the position of a light or this kind of details... Events will be action: spawn childs, trigger animations, detach payloads and whatever ideas can come out, so it will both to code and to test much more fun.
jedidia
shoemaker without legs
I think he meant more funny for him to develop.
yes, even though I think that it will be the fun part also for the users in the end
Why not?
my idea is to put a series of possible events, and a series of conditions that will trigger them and then the user will build his own combinations.
Up to now my ideas were:
possible events:
- spawning of a child
- triggering of an animation
- firing of a thruster/thruster group
- vessel partial/total reconfiguration
- payload jettison
possible triggers:
- keypress
- altitude threshold (from below or from above)
- fuel tank level threshold
- velocity threshold (from below or from above, meters/second or mach)
- time limit (mjd or missione elapsed time)
I now would add texture exchange as a possible event and a dynamic pressure threshold as a possible trigger.
---------- Post added 9th Mar 2019 at 13:43 ---------- Previous post was 8th Mar 2019 at 22:13 ----------
Variable Drag Elements section up and running...
The pre-release part is basically over.
I also added a new command in thruster_group section which creates a default RCS system. This allow to have with just one click a complete set of thrusters and thruster groups that allow to steer the vehicle. Thrusters and group will just then appear in their relevant sections so the user will then be able to customize them at wish. I think that it will be an option very often used.
I also changed a bit also the automatic backup procedure of the configs: after I realized that due to a glitch I lost a lot of settings of the DG example I decided that the backup procedure was not enough, so now, instead of just a copy of the old cfg, the module creates a txt file where it appends all the backups marked with the system date. This means that the backup file can become big after many open and close of the editor, but the user won't lose a single data and will have the full story of its vessel during development in that file, and in case he can erase part of it or the whole file if he wants to free space. Anyway we are talking about txt files, so it could become a couple of MB after some hundreds of opening and closing, so nothing serious.
So I want to do two things more before posting the pre release:
- Prepare a good Log functionality so everything will be logged and easy to trace
- Finalize a small set of examples (DG, robotic arm, Cupola, first section of the ISS).
And then the pre-release will be posted here.
Hey Don... It seems to me that with 3 working MFDs is even better 
---------- Post added at 16:47 ---------- Previous post was at 15:04 ----------
Here it is, the pre-release! it is a sort of pre-alpha so expect things not working 100%. three examples are included (DeltaGlider, Cupola and SSRMSD). For Cupola and SSRMSD the ISS A to Z package is needed. For those who does not have the package there is a "only DG" scenario.
I didn't have time to include also the first small part of the ISS A to Z but it will come soon.
There is a synthetic doc that explains the keys and some notes. For the rest I believe that the dialog is quite intuitive and anyway I wanted to module to start to be used while I prepare the final version and the whole set of documentation section by section. So feel free to ask your questions here. I have a busy week in front of me but I will try to give all the answers in the short time frame possible.
Let me know guys... I hope for the best!
Fred
VesselBuilder1_PreRelease.zip
---------- Post added at 16:47 ---------- Previous post was at 15:04 ----------
Here it is, the pre-release! it is a sort of pre-alpha so expect things not working 100%. three examples are included (DeltaGlider, Cupola and SSRMSD). For Cupola and SSRMSD the ISS A to Z package is needed. For those who does not have the package there is a "only DG" scenario.
I didn't have time to include also the first small part of the ISS A to Z but it will come soon.
There is a synthetic doc that explains the keys and some notes. For the rest I believe that the dialog is quite intuitive and anyway I wanted to module to start to be used while I prepare the final version and the whole set of documentation section by section. So feel free to ask your questions here. I have a busy week in front of me but I will try to give all the answers in the short time frame possible.
Let me know guys... I hope for the best!
Fred
VesselBuilder1_PreRelease.zip
Kyle
Armchair Astronaut
This is seriously fantastic Fred. I've been playing around for a bit and I haven't noticed any major issues yet. This has potential to save a lot of defunct addons that are no longer compatible with Orbiter 2016.
please try the module because everything is there. you can do pretty much whatever you want.
---------- Post added at 20:48 ---------- Previous post was at 19:46 ----------
A couple of notes more that I will add in the doc:
- Remember to press the various "SET" buttons when you change your values otherwise they won't be applied.
- For touchdown points, in the SET1 window there is the button "Just Some Default Points Please..." which clears the set and create a set of 4 points which should work with the current mass of the vessel. Anyway they won't be applied right away, they will just be put in the list, and in any case once you are done with the list you have to press "APPLY" to actually apply the list of TD Points. You can easily check visually this with the "Show this SET" and "Show Current Points" options. Current Points means the TD Points that the vessel has in that moment.
Minimum config for the moment is:
I suspect that are not defined default value for those parameters.
I recommend to use [ALT] instead of [CTRL] (camera is controlled by this configuration)
[CTRL]+[RIGHT ARROW]/[LEFT ARROW] = If in Grapple Mode -> choose next/previous attachment
I also tested variable ISP - it works as expected.
Great work! :thumbup:
Code:
ClassName = VesselBuilder1
Module = VesselBuilder1
TDP_SECONDSET_ENABLED = FALSE
TDP_CHANGEOVER_ANIM = -1I suspect that are not defined default value for those parameters.
I recommend to use [ALT] instead of [CTRL] (camera is controlled by this configuration)
[CTRL]+[RIGHT ARROW]/[LEFT ARROW] = If in Grapple Mode -> choose next/previous attachment
I also tested variable ISP - it works as expected.
Great work! :thumbup:
Last edited:
Minimum config for the moment is:
Code:ClassName = VesselBuilder1 Module = VesselBuilder1 TDP_SECONDSET_ENABLED = FALSE TDP_CHANGEOVER_ANIM = -1
I suspect that are not defined default value for those parameters.
I recommend to use [ALT] instead of [CTRL] (camera is controlled by this configuration)
[CTRL]+[RIGHT ARROW]/[LEFT ARROW] = If in Grapple Mode -> choose next/previous attachment
I also tested variable ISP - it works as expected.
Great work! :thumbup:
Ah yes those parameters get written also if not needed, I will take them out. And well received the suggestion on the keys, thanks that's exactly the reviews I am looking for! :tiphat:
Kyle
Armchair Astronaut
I get a CTD whenever I try to reload a scenario, here's my log:
Code:
**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 2.55137e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Module AtlantisConfig.dll .... [Build 160828, API 160828]
000000.000: Module AtmConfig.dll ......... [Build 160828, API 160828]
000000.000: Module DGConfigurator.dll .... [Build 160828, API 160828]
000000.000: Module ProjectApolloConfigurator.dll [Build 181118, API 160828]
000000.000: Module ProjectOutpostsConfig.dll [Build 120604, API 100830]
000000.000: Module InterMFD56.dll ........ [Build 160829, API 160815]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiRegisterMFDMode
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.000: Module LunarTransferMFD.dll .. [Build 160829, API 160815]
000000.000: Module ScnEditor.dll ......... [Build 160828, API 160828]
000000.000: Module Rcontrol.dll .......... [Build 160828, API 160828]
000000.000: Module Framerate.dll ......... [Build 160828, API 160828]
000000.000: Module FlightData.dll ........ [Build 160828, API 160828]
000000.000: Module ExtMFD.dll ............ [Build 160828, API 160828]
000000.000: Module DX9ExtMFD.dll ......... [Build 150812, API 100830]
000000.000: Module Multistage2015_MFD.dll [Build 170531, API 160828]
000000.000: Module PursuitMFD_2016.dll ... [Build 160917, API 160828]
000000.000: Module AeroBrakeMFD.dll ...... [Build ******, API 100830]
000000.000: Module DscovrMFD.dll ......... [Build 150205, API 100830]
000000.000: Module CRT.dll ............... [Build ******, API 060425]
000000.000: Module LoadMFD2.dll .......... [Build 161223, API 161124]
000000.000: Module CamShake.dll .......... [Build 100811, API 100606]
000000.000: ---------------------------------------------------------------
BaseDir : C:\Orbiter 2016\
ConfigDir : C:\Orbiter 2016\Config\
MeshDir : C:\Orbiter 2016\Meshes\
TextureDir : C:\Orbiter 2016\Textures\
HightexDir : C:\Orbiter 2016\Textures2\
ScenarioDir: C:\Orbiter 2016\Scenarios\
000000.000: ---------------------------------------------------------------
000000.000: Module D3D9Client.dll ........ [Build 190225, API 160828]
000000.000: Module ProjectApolloMFD.dll .. [Build 181118, API 160828]
000000.000: Module CamControl.dll ........ [Build ******, API 050206]
000000.000: Module RPOP.dll .............. [Build 111124, API 100830]
000000.000: Module VirtualNumPad.dll ..... [Build ******, API 060425]
000000.000: Module LaunchMFD.dll ......... [Build 180706, API 160828]
000000.000: Module transx.dll ............ [Build 160216, API 160214]
000000.000: Module CustomMFD.dll ......... [Build 160828, API 160828]
000000.000: Module uap.dll ............... [Build 110613, API 100830]
000000.000: Module RV_Orientation.dll .... [Build 180811, API 160828]
000000.000: Module OrbiterSound.dll ...... [Build 121120, API 100830]
000000.000: Module Damage.dll ............ [Build 130104, API 111029]
000000.000: Module LuaMFD.dll ............ [Build 160828, API 160828]
000000.000:
000000.000: **** Creating simulation session
000000.000: D3D9: [DirectX 9 Initialized]
D3D9: 3D-Adapter.............. : AMD Radeon (TM) R9 380 Series
D3D9: MaxTextureWidth......... : 16384
D3D9: MaxTextureHeight........ : 16384
D3D9: MaxTextureRepeat........ : 8192
D3D9: VolTexAddressCaps....... : 0x3F
D3D9: NumSimultaneousRTs...... : 4
D3D9: VertexDeclCaps.......... : 0x3FF
D3D9: MiscCaps................ : 0x3FCCF2
D3D9: XNA Math Support........ : Yes
D3D9: Vertex Texture.......... : Yes
D3D9: Shadow Mapping.......... : Yes
D3D9: D3DFMT_A16B16G16R16F.... : Yes
D3D9: D3DFMT_A32B32G32R32F.... : Yes
D3D9: D3DFMT_D32F_LOCKABLE.... : Yes
D3D9: D3DFMT_A2R10G10B10...... : Yes
D3D9: D3DFMT_L8............... : Yes
D3D9: D3DDTCAPS_DEC3N......... : Yes
D3D9: D3DDTCAPS_FLOAT16_2..... : Yes
D3D9: D3DDTCAPS_FLOAT16_4..... : Yes
D3D9: Runs under WINE......... : No
D3D9: Available Texture Memory : 4080 MB
000000.000: D3D9: [3DDevice Initialized]
000000.000: D3D9: [Loading Constellations]
000000.000: D3D9: [D3D9Client Initialized]
000000.000: Module Sun.dll ............... [Build 160828, API 160828]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 160828, API 160828]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 160828, API 160828]
000000.000: Module VenusAtm2006.dll ...... [Build 160828, API 160828]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 160828, API 160828]
000000.000: Module EarthAtmJ71G.dll ...... [Build 160828, API 160828]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 160828, API 160828]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 160828, API 160828]
000000.000: Module MarsAtm2006.dll ....... [Build 160828, API 160828]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
000000.000: Module Phobos.dll ............ [Build ******, API 060425]
000000.000: Module Deimos.dll ............ [Build ******, API 060425]
000000.000: Module Galsat.dll ............ [Build 160828, API 160828]
000000.000: Module Jupiter.dll ........... [Build 160828, API 160828]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 160828, API 160828]
000000.000: Module Europa.dll ............ [Build 160828, API 160828]
000000.000: Module Ganymede.dll .......... [Build 160828, API 160828]
000000.000: Module Callisto.dll .......... [Build 160828, API 160828]
000000.000: Module Satsat.dll ............ [Build 160828, API 160828]
000000.000: Module Saturn.dll ............ [Build 160828, API 160828]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 160828, API 160828]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 160828, API 160828]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 160828, API 160828]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 160828, API 160828]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 160828, API 160828]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 160828, API 160828]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 160828, API 160828]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 160828, API 160828]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
000000.000: Module Miranda.dll ........... [Build ******, API 060425]
000000.000: Module Ariel.dll ............. [Build ******, API 060425]
000000.000: Module Umbriel.dll ........... [Build ******, API 060425]
000000.000: Module Titania.dll ........... [Build ******, API 060425]
000000.000: Module Oberon.dll ............ [Build ******, API 060425]
000000.000: Module Neptune.dll ........... [Build 160828, API 160828]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world
000000.000: Module VesselBuilder1.dll .... [Build 190310, API 160828]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: VESSEL::CreateVariableDragElement
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------In the config\vessels\vesselbuilder1\logs folder there shall be the log file of the vessel you were trying to load, could you post that?
Kyle
Armchair Astronaut
I figured it out, I was incorrectly defining the default parameters of my vessel and getting a CTD as a result. Fixed now, works fine.
