New Release Interplanetary Modular Spacecraft RC9

Inksoull said:
That fixes it :) brilliant, thank you! Why couldn't I find this anywhere before?
Click to expand...

Because most of orbinauts are turning this option on right after they installed Orbiter and forgetting about it for good :lol: Don't worry, there're many hidden things like this in Orbiter and IMS both.
 
Last edited:
Because most of orbinauts are turning this option on right after they installed Orbiter and forgetting about it for good
Click to expand...

Not quite, and frankly the crashes between launches are really just sloppiness on the part of IMS. The trouble is, I can't find the bloomin' cause. There's no leaks left, but still there must be something that isn't correctly freed or redefined, but stack variables in vessel modules don't remain valid anyways between simulation exits, so I really have no Idea what it's about... yet.

So I can fix that issue by editing the scenario file?
Click to expand...

Yes and no. The issue will be there again everytime you SQL with active live support until I get RC5 up. If you go to the CONSUMABLES line, the structure is max current regen, three times. Just set the regen value to zero.

I wouldn't go to any great lengths to fix it in this version, just remember so that we don't make the mistake in IMS2.
Click to expand...

It's practically impossible to repeat, since this bug is the consequences of old code not being revised properly when changes were made.

On that topic, what is the status with IMS2?
Click to expand...

Waiting for me to finish IMS and be done with it.
 
IMS 1.0 done?

jedidia said:
Waiting for me to finish IMS and be done with it.
Click to expand...

Didn't you know Jedidia that software is NEVER done, it just escapes? ;)

I hope you're not waiting for me to finish the Lunar Station in IMS 1.0... I just did mission 105 last night and I'm now estimating it will take around 500 missions to finish it. At this rate, I should be done around the summer time... of 2016!

Dantassii
HUMONGOUS IMS shipbuilder
 
Didn't you know Jedidia that software is NEVER done, it just escapes?
Click to expand...

Software may never be done. I, on the other hand... :lol:

---------- Post added at 01:50 PM ---------- Previous post was at 12:05 PM ----------

Just great! I know now what causes the crash on reload if launchpad wasn't closed.

It's shifting the CoG during clbkLoadState :facepalm:

I'll see if anything can be done about this behavior, or if this is an orbiter issue. For starters, I'll try to reproduce it with a shuttlePB.
 
jedidia said:
Just great! I know now what causes the crash on reload if launchpad wasn't closed.

It's shifting the CoG during clbkLoadState :facepalm:

I'll see if anything can be done about this behavior, or if this is an orbiter issue. For starters, I'll try to reproduce it with a shuttlePB.
Click to expand...

add in a simt>1 frame condition for the updater in the step updater? (I dont know whether IMS uses prestep or poststep)
 
add in a simt>1 frame condition for the updater in the step updater? (I dont know whether IMS uses prestep or poststep)
Click to expand...

Not the problem. The shift was moved to LoadState because otherwise the touchdown points go haywire.
 
The ship moves on the ground.

I reproduced the behavior perfectly with a shuttlePB. There's no doubt that this is an orbiter issue, and I don't expect it to get fixed before the next version either. So we'll just have to live with it. After everything I managed to fix it itches a bit, but it's really minor. With the bugfixes done today I think I'm practically finished. I'll upload RC5 tomorrow, then I'll start updating some of the documentation, and when we have things together and there's not been other bugs, I'll put it on the hangar.
 
jedidia said:
The ship moves on the ground.

I reproduced the behavior perfectly with a shuttlePB. There's no doubt that this is an orbiter issue, and I don't expect it to get fixed before the next version either. So we'll just have to live with it. After everything I managed to fix it itches a bit, but it's really minor. With the bugfixes done today I think I'm practically finished. I'll upload RC5 tomorrow, then I'll start updating some of the documentation, and when we have things together and there's not been other bugs, I'll put it on the hangar.
Click to expand...

As in, moves sideways, or the TDpoints are underground, sending the ship to NANspace?

I like the sounds of that, although I dont know how much of the docs are ready yet. Goaowonk did some edits to the documentation, but I dont know how close we are to what you want for a release candidate. Would you like me to send you the link that he sent me for it?
 
As far as I can tell it didn't happen in previous versions, but I've noticed that sealed CM's bump their weight up to 1.06047e+292 at scenario reload, and that unsealed CM's are equally as over weight for the first ten seconds of simulation time.
 
Inksoull said:
As far as I can tell it didn't happen in previous versions, but I've noticed that sealed CM's bump their weight up to 1.06047e+292 at scenario reload, and that unsealed CM's are equally as over weight for the first ten seconds of simulation time.
Click to expand...

:blink:

Ten seconds? Looks like the refreshing period of SetCenterOfGravity, need to check this.
 
Your code is very much out of date, I doubt you'll find anything. I'll take a look at it when I get the time.
 
The problem is I can't reproduce the issue reported by Inksoull, but I have another one which seems somewhat similair. When I get my storages full and save I have this string in the scenario file:

Code: 
  CONSUMABLES 1536 1536 0 6520 6520 0 1100 6.39721e-289 0

Predictably, I have zero food when starting the scenario.

I'm not sure either if thes strings are correct:

Code: 
  RADIATOR 11 284.325 2.22045e-016 -1 -2.77556e-016 -1 16 17
  RADIATOR 12 186.308 -5.55112e-017 1 1.11022e-016 2 5


---------- Post added at 13:01 ---------- Previous post was at 12:51 ----------

It only happens in RC5, nothing like that in RC4 with the same conditions.
 
Hey, I tried the IMS RC5 version and got a CTD as soon as I load up any IMS modules. This happened first on the D3D9 RC12 client, so I tried it on a clean Orbiter installation and got the same thing.

When I load a scenario containing IMS modules, the sim freezes upon loading burchismo/SBB104.dds and gives the following:
Code: 
**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 2.49726e-007 sec
Found 1 joystick(s)
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (NVIDIA GeForce GTX 470)
==> Direct3D T&L HAL (NVIDIA GeForce GTX 470)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1914 x 1052 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: 8
Loading 15382 records from star database
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build 100215, API 100212]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll ............. [Build 100215, API 100212]
SATSAT Mimas: Terms 113
Module Enceladus.dll ......... [Build 100215, API 100212]
SATSAT Enceladus: Terms 33
Module Tethys.dll ............ [Build 100215, API 100212]
SATSAT Tethys: Terms 101
Module Dione.dll ............. [Build 100215, API 100212]
SATSAT Dione: Terms 59
Module Rhea.dll .............. [Build 100215, API 100212]
SATSAT Rhea: Terms 68
Module Titan.dll ............. [Build 100215, API 100212]
SATSAT Titan: Terms 100
Module Iapetus.dll ........... [Build 100215, API 100212]
SATSAT Iapetus: Terms 605
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
Module DeltaGlider.dll ....... [Build 100830, API 100830]
Module LuaInline.dll ......... [Build 100830, API 100830]
Module ShuttleA.dll .......... [Build 100830, API 100830]
Module ShuttlePB.dll ......... [Build 100830, API 100830]
Module IMS.dll ............... [Build 131003, API 100830]

I suspected it could be a problem on my end with a missing mesh but I copied and pasted the files for SSBB 4.0 then 4.1B, and found the problematic mesh file was present in my textures folder.
 
That is rather strange... RC5 didn't really change anything connected to those. Looks more like the result of an out-of-bounds operation.

I'll see what I can come up with.

---------- Post added at 08:17 AM ---------- Previous post was at 08:07 AM ----------

Forgett the above. The problem is quite clear and has to do with a sloppy fix of the regen saving problem from RC4. I forgott to uncomment a line I commented for testing purposes :oops:

That would not, however, explain the mass of the CM going haywire. Inksoull, could you post more detailed reproduction steps (I.E. click by click!), as none of us are so far able to reproduce the behavior with the information you provided.

The radiator entries are ok, they just weren't rounded. Will have to fix that.
 
Last edited:
jedidia said:
Inksoull, could you post more detailed reproduction steps (I.E. click by click!)
Click to expand...

Can do.

1. Start up Orbiter.exe

2. Open scenario: Delta-Glider/Cape Canaveral

3. F4

4. Custom ...

5. Scenario Editor

6. New ...

7. Type "BM201" for the vessel name

8. Open vessel: IMS/Command_Modules/BM201_Control_Module

9.Create ...

10. Ctrl-Q (Respawning the window)

11. Launch "Current State"

12. Ctrl-I


I reproduced the haywire weight situation twice just now following this.
 
Inksoull said:
Can do.

1. Start up Orbiter.exe

2. Open scenario: Delta-Glider/Cape Canaveral

3. F4

4. Custom ...

5. Scenario Editor

6. New ...

7. Type "BM201" for the vessel name

8. Open vessel: IMS/Command_Modules/BM201_Control_Module

9.Create ...

10. Ctrl-Q (Respawning the window)

11. Launch "Current State"

12. Ctrl-I


I reproduced the haywire weight situation twice just now following this.
Click to expand...

No repro on that. Could you post the content of (Current state).scn as it is in between step 10 and step 11?
 
New Question from Dantassii

Ok, I've got a question and it may not have an answer, but here goes.

When I use the XR5 Payload manager to put IMS modules into the payload bay, the payload manager comes up with HUMONGOUS names for each module based on the modules name, its full description, the directory that it's located, and the location where it's attached to the payload bay of the XR5. My question is this:

Q) Is there any way to rename the module after it's been placed in the payload bay short of shutting down Orbiter, opening the scenario file in notepad, and manually editing the module names in the scenario file?

I've been doing this since mission 1 on my Lunar Station building and now that I've gotten up to mission 107 it's getting to be rather annoying to have to open and shift through a HUMONGOUS scenario file just to get to the bottom to change the names on 2 dozen new modules that I'm adding each mission.

Dantassii
HUMONGOUS IMS shipbuilder
 
You must log in or register to reply here.

Similar threads

llarian
Software How to setup and name mesh groups in Blender for use in Vinka's Spacecraft ...
Replies
6
Views
1K
gattispilot
gattispilot
N
Problem SSV not loading in Orbiter 2024
Replies
5
Views
1K
CuriousDude?_
C
J
Problem D3D9 not working with orbiter 2024
2
Replies
34
Views
6K
Banshii59
B
n72.75
  • Poll Poll
Ease of changing simulation paramteters.
Replies
1
Views
1K
misha.physics
misha.physics
Tiny_Bob
SDK Question New to addon creation, looking for a good place to start
Replies
10
Views
2K
Matias Saibene
Matias Saibene
Back
Top