New Release Interplanetary Modular Spacecraft RC9

[jedidia]

Sredstva udruženja koristi će se za pokriće redovnih troškova i aktivnosti udruženje, te i za nabavku potrebne opreme za stecanje ciljeva udruženje.

His card does have DX10 support with the appropriate drivers, AFAIK.

When viewing my Lunar Station or SSTV vehicles, getting frame rates higher than 10 FPS is really nice.

On my laptop, I get a slide show. On my rig I get around 40 to 50, despite it having a processor that is by now almost a decade old... GPU is everything nowadays (well, until you start multi-channel studio recording... then you suddenly realise that RAM and HD-access are everything. To every trade its tool, I guess...)

 

[paradineai]

When my (at the time) 6 year old graphics card died a couple years ago, I got a significant improvement in FPS in Orbiter by getting the cheapest video card available that used 'current' technology. I think I spent $50 on the new card. Your video card may be so old that it has questionable DXD9 support. But current technology cards have at least DXD11 support. You may want to try getting a newer (but cheap!) video card.

I'm using a dell laptop. not a tower pc

---------- Post added at 11:29 AM ---------- Previous post was at 11:18 AM ----------

this is my current setup

 

[jedidia]

I just got my crew killed by a heat surge at orbiter startup. I noticed that oftentimes, the temperatures went up by a Kelvin or two when starting a scenario. This particular one had some issue, it hung a few seconds before the sim screen appeared.

That made me suspicious, and I made some tests to measure the delta time of the first frames. To my surprise, exactly the first three frames are of fixed length: 0.01 seconds. Only then do they start to varry. Presumably orbiter does something during those first three frames, and afterwards it can lag a bit.

Anyways, it shows that for all my trying, the stepping in the thermodynamics code still isn't save. I'll have to do something about that, I guess...

---------- Post added at 10:35 PM ---------- Previous post was at 10:15 PM ----------

What do you know... It's got nothing to do with the stepping. The radiators status doesn't get updated to "deployed" after startup until you access the engineering panel for the first time! :facepalm:

Now there's a serious bug to go unnoticed for so long :shifty:

 

[Dantassii]

What do you know... It's got nothing to do with the stepping. The radiators status doesn't get updated to "deployed" after startup until you access the engineering panel for the first time! :facepalm:

Now there's a serious bug to go unnoticed for so long :shifty:

Glad you got to the bottom of that one Jedidia.

Dantassii
HUMONGOUS IMS shipbuilder

 

[Matias Saibene]

Excuse my ignorance, but how I can get the latest version of Interplanetary Modular Spacecraft?
I've looked at OMH and does not appear.

I would appreciate your response, I download it because it seems a very interesting add-on.

 

[jedidia]

It's not on OrbitHangar because it's not officially released yet. There is however a quite visible link to the current version on the first page of this thread

 

[Matias Saibene]

There is however a quite visible link to the current version on the first page of this thread

Thanks, actually see the link, but I wanted to make sure it was the latest version.

 

[Mandella]

So I finally decided that try out this program, and of course I am having issues.

On a clean install with only SSBB41, Orbitersound40, UGCO20 and IMS installed and running vanilla graphics client everything seems to work just fine until I decide to save and reload the scenario, in which case CTD. Doesn't matter if I have or have not removed the transport wrapper, or have integrated the parts or not.

I'm running Windows 7-64bit with an NVidia GTX 550TI, all fully up to date with drivers. AMD Phenom 3.4 GHz, 8 Gigs RAM. I'm running Orbiter on an SSD, but I have the same error when I move the install to another disk.

Orbiter Log:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 2.77927e-007 sec
Found 0 joystick(s)
Devices enumerated: 9
Devices accepted: 7
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (NVIDIA GeForce GTX 550 Ti)
==> Direct3D T&L HAL (NVIDIA GeForce GTX 550 Ti)
==> Direct3D HAL (NVIDIA GeForce GTX 550 Ti) #2
==> Direct3D T&L HAL (NVIDIA GeForce GTX 550 Ti) #2
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]
Module LuaConsole.dll ........ [Build 100830, API 100830]
Module transx.dll ............ [Build 100824, API 100823]
Module OrbiterSound.dll ...... [Build 121120, API 100830]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1274 x 692 x 32
Graphics: Hardware T&L capability: No
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: -1
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 IMS.dll ............... [Build 090123, API 100830]

Latest Scenario File:

BEGIN_DESC
Contains the latest simulation state.
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 53829.8512700862
END_ENVIRONMENT

BEGIN_FOCUS
  Ship Luna-OB1
END_FOCUS

BEGIN_CAMERA
  TARGET Locus
  MODE Extern
  POS 4.71 51.82 -11.37
  TRACKMODE GlobalFrame
  FOV 40.00
END_CAMERA

BEGIN_SHIPS
Luna-OB1:Wheel
  STATUS Orbiting Moon
  RPOS -156876.67 2232308.87 410.57
  RVEL -1476.330 -103.966 0.187
  AROT -0.00 -0.00 123.10
  VROT 0.00 0.00 10.00
  AFCMODE 7
  IDS 0:560 100 1:564 100
  XPDR 494
END
Locus:IMS\Command_Modules\BM201_CONTROL_MODULE
  STATUS Orbiting Earth
  RPOS 7004096.55 0.00 237173.51
  RVEL -255.231 -0.000 7537.365
  AROT 0.00 -0.00 0.00
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:1.000000 2:1.000000
  NAVFREQ 0 0
  COMMAND 0 1
  TDPOINT 0,0,0 0,0,0 0,0,0
  EMPTYMASS 10000.000000
  MASSCENTER 0.000000 0.000000 0.000000
  PMI 8.150000 8.150000 2.300000
  CONSUMABLES 0.0001 0.0001 0 0.0001 0.0001 0 0.0001 0.0001 0
  TEMPERATURES -1:298.00:273.06
  HEATING -1
  THGROUPLEVELS 0 0 0 0 
  CREW 2 0
  ENERGY 396000000.000000
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
END
END_SHIPS

It looks like I've got proper shortcuts in the /Modules/Server directory. (Config and Sound.)

Anybody got an idea what's up?

 

[PeterRoss]

Module IMS.dll ............... [Build [COLOR="Red"]090123[/COLOR], API 100830]

Uh, Jedidia, maybe you should have your motherboard battery replaced?

 

[jedidia]

On a clean install with only SSBB41, Orbitersound40, UGCO20 and IMS installed and running vanilla graphics client everything seems to work just fine until I decide to save and reload the scenario, in which case CTD. Doesn't matter if I have or have not removed the transport wrapper, or have integrated the parts or not.

Scenario works flawlessly over here, there's nothing wrong in the log. One question: Did you try to reload the scenario without quitting the launchpad after the last session ended?

IMS causes a crash in that case, because of some orbiter bug that causes a ctd on scenario reload when there's calls to ShiftCG in the vessels initialisation (and IMS needs to do it there).

Uh, Jedidia, maybe you should have your motherboard battery replaced?

It's probably because I took it appart several times lately (which for this laptop means disconnecting the battery). I wasn't aware that Visual Studio gets the date from the hardware instead of from the OS...

 

[Mandella]

Thanks for looking at this so quickly.

I've found an apparent fix for my problem -- just run orbiter in compatibility mode (XP Service pack 3). It loads fine then, although I haven't had a chance to play with it much to see if there are any other save/load issues.

Thanks again! I'm looking forward to getting a lot of use out of this addon...

 

[jedidia]

I've found an apparent fix for my problem -- just run orbiter in compatibility mode (XP Service pack 3).

Huh? I'm running it in 7 64 bit all the time... ??

 

[Dantassii]

Windows 8 had some issues

When I tried to run Orbiter 2010 on my Dad's Windows 8 machine it did some really weird things. Like all the dialog boxes that popup could not be closed and several MFDs caused it to CTD.

'course when we tried to view my Lunar Station in orbit, we got about 5 seconds per frame on the frame rate.

Dantassii
HUMONGOUS IMS shipbuilder

 

[Mandella]

Huh? I'm running it in 7 64 bit all the time... ??

Well, I also note that as long as I check the compatibility box it will run in almost any mode (including Windows 7) but it CTDs with the box unchecked.

I have no idea. I guess we can just chalk it up to some odd chance issue with my unique combination of software and hardware on this machine.

Dantassi, did you try checking the compatibility box on your Dad's Win8 machine?

 

[Dantassii]

Dantassii, did you try checking the compatibility box on your Dad's Win8 machine?

He's running it in Windows 8 mode and isn't interested in messing with it. As it was, I uninstalled Orbiter 2010 as soon as we finished looking at it so it's not an issue. I just hope that by the time I'm forced to upgrade to Windows 8+ that the next version of Orbiter will be out and it will work out-of-the-box in that OS. My computer runs Windows 7, 64 bit, and I've never had any compatibility issues.

Dantassii
HUMONGOUS IMS shipbuilder

 

[Buck Rogers]

Just playing around with IMS; a very small un-finalised ship, came across this repeatable bug:
Under the control panel I have only 2 entries:
1 Solarpanel
2 Solarpanel
clicking on each highlights and brings up rel. data bottom right.
clicking next to or below causes instant CTD; unknown software error!
other panels seem to be OK

hopefully a useful bug report - best regards

 

[jedidia]

A scenario to go along with that would be helpful. Meanwhile, I think I actually fixed this one... I just never got around to upload the current version which has quite a few minor and major bugs fixed. Will do so somewhen this week.

 

[Buck Rogers]

no quicker said than done:

BEGIN_DESC
Contains the latest simulation state.
END_DESC

BEGIN_ENVIRONMENT
  System Sol_test
  Date MJD 51982.6474448624
END_ENVIRONMENT

BEGIN_FOCUS
  Ship CisLunarShuttle
END_FOCUS

BEGIN_CAMERA
  TARGET CisLunarShuttle
  MODE Extern
  POS 3.57 -143.14 13.33
  TRACKMODE GlobalFrame
  FOV 50.00
END_CAMERA

BEGIN_HUD
  TYPE Orbit
  REF AUTO
END_HUD

BEGIN_PANEL
END_PANEL

BEGIN_SHIPS
CisLunarShuttle:IMS\Command_Modules\BM201_CONTROL_MODULE
  STATUS Orbiting Earth
  RPOS -3594659.02 -6714.47 6004248.31
  RVEL -6485.502 -6.746 -3881.074
  AROT -153.68 -40.68 -139.70
  VROT -5.38 5.79 -2.62
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:1.000000 2:1.000000 3:0.979396 4:0.997479
  NAVFREQ 0 0
  COMMAND 1 0
  MODULE Docking_Ports\DAAPAS_Docking_Adapter 0,0,5.0761 0,0,1 0,1,0 0
  MODULE Fuel_Tankage\BTank202_LOX_LH2_SFuelTank 0,0,-6.1839 0,0,1 0,1,0 0
  MODULE Truss_Parts\BT100_Truss 0,0,-8.3809 1,0,0 0,-1,0 0
  MODULE Fuel_Tankage\BTank101_LH2_LFuelTank -7.3165,0,-8.3806 0,0,1 0,1,0 0
  MODULE Fuel_Tankage\BTank101_LH2_LFuelTank 7.3165,0,-8.3806 0,0,1 0,-1,0 0
  MODULE Radiators\Radiator_64 7.3164,-2.741,-8.381 0,-1,0 0,0,-1 0
  MODULE Radiators\Radiator_64 -7.317,-2.741,-8.3802 0,-1,0 0,0,-1 0
  MODULE Power_Generation\SolarArrayCirc_3m 7.3164,2.741,-8.381 0,1,0 1,0,0 0
  MODULE Power_Generation\SolarArrayCirc_3m -7.317,2.741,-8.3802 0,1,0 1,0,0 0
  MODULE Propulsion\BRCS1_ReactionControlSystem_Engine -9.957,0,-8.3802 -1,0,0 0,0,1 0
  MODULE Propulsion\BRCS1_ReactionControlSystem_Engine 9.9574,0,-8.381 1,0,0 0,0,1 0
  MODULE Propulsion\NERVA 0,0,-13.9096 0,0,1 1,0,0 0
  MODULE Batteries\BG201_Battery_SContainer 0,-2.3574,-8.3806 1,0,0 0,1,0 0
  TDPOINT 0,0,0 0,0,0 0,0,0
  DELETEPOINT 2
  DELETEPOINT 1
  ATTPOINT IM 0,1.089,-8.3806 0,1,0 1,0,0
  ATTPOINT IM 0,-3.626,-8.3806 0,-1,0 1,0,0
  DELETEPORT 1
  DELETEPORT 0
  DOCKPORT 0,0,5.426 0,0,1 0,1,0
  CONSTRUCTIONPORT 0,1.089,-8.3806 0,1,0 1,0,0
  CONSTRUCTIONPORT 0,-3.626,-8.3806 0,-1,0 1,0,0
  EMPTYMASS 26240.000000
  MASSCENTER -0.000012 -0.064908 -7.502700
  PMI 111.020000 115.230000 56.680000
  PROP LOX_LH2 5680 5562.97
  PROP LH2 18984 18936.1
  ENGINE 11 0 0
  RCSBLOCK 4 1000 4099 -9.957,0,-8.3802 5 0,0,1 0,-1,0 0,0,-1 0,1,0 1,0,0 1
  RCSBLOCK 4 1000 4099 9.9574,0,-8.381 5 0,0,1 0,1,0 0,0,-1 0,-1,0 -1,0,0 1
  ANIM 5 Radiators\Radiator_64 1 1
  ANIM 6 Radiators\Radiator_64 1 1
  ANIM 7 Power_Generation\SolarArrayCirc_3m 1 1
  ANIM 8 Power_Generation\SolarArrayCirc_3m 1 1
  CONSUMABLES 0.0001 0.0001 0 0.0001 0.0001 0 0.0001 0.0001 0
  TEMPERATURES -1:299.43:246.60 7:237.37:330.00 8:237.37:330.00 11:879.51:246.68 12:298.27:245.56
  RADIATOR 5 268.93 -1.11022e-016 0 -1 -1 11 7 12
  RADIATOR 6 232.169 -1.66533e-016 4.33681e-019 -1 -1 11 8 12
  HEATING -1 11
  THGROUPLEVELS 0 0 0 0 
  CREW 2 0
  ENERGY 1169502554.175546
  SOLARARRAY 7 1 0 0.263723 0.384960 0.669440 0.422871
  SOLARARRAY 8 1 0 0.263723 0.384960 0.669440 0.422871
  MFC 0 1 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 1 1 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 1 0 7 0 0 0 -1
  MFC 0 1 3 0 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
  MFC 0 0 0 -1 -1 -1 -1
END
END_SHIPS

BEGIN_uap
END

BEGIN_ReFuelMFD
  SCENARIO_TREE 
    NAMED Computers
    END_NODE 
  END_NODE 
END

by the way definitely not an example of good ship building, small also seems to have its disadvantages as far as available RCS allocation is concerned!
you may have no legs but you make great shoes! keep up the good work:thumbup:

 

[jedidia]

Finally I remember to upload this thing. I'm sorry for the delay. My head had its periodical off-time from space these last 3 months (a time during which it mostly plays old-school fantasy RPGs).

RC9 has undergone some actual playtesting (i.e. actually flying around and using a built ship, not just putting stuff together and see if it works correctly for a few seconds), and therefore fixes quite a few bugs that were never encountered much before.

Most grieviously, heat did not dissipate until the engineering panel was accessed for the first time in a session. That went unnoticed since people were mostly busy building, but when you're on a trip, save the scenario, later reload, check your course and get fried 10 seconds in, it gets pretty annoying...

Other stuff include a problem with custom animation names that could in the worst case lead to a ctd. Since they were only ever used for general purpose modules, noone noticed so far.

There's a few other minor things as well, which I forgot in the meantime. All in all, this version should be perfectly stable and usable for any sane purposes (**looks sternly at Dantassii**). Once I get some proper documentation going I think I can call this bygones. And maybe even continue with IMS2. Wouldn't that be nice...

 

[Dantassii]

...There's a few other minor things as well, which I forgot in the meantime. All in all, this version should be perfectly stable and usable for any sane purposes (**looks sternly at Dantassii**). Once I get some proper documentation going I think I can call this bygones. And maybe even continue with IMS2. Wouldn't that be nice...

With RC 8:

I don't know if this is fixed in RC9 or if it's part of Orbiter 2010 P1 that can't be fixed by IMS but I still find that certain modules (BCRS2s are doing it right now) tend to have problems if you create more than a certain number of them with names that only vary by 1 character. BCRS2s break on groups of 112, BT101's break in groups of 10.

Since I use hundreds of BT101's and I currently have dozens of BCRS2s, I've had to come up with some creative naming conventions to keep this from crashing.

The crash occurs not when you add them to the scenario, not when you dock them together, but when you have docked them all together, save the scenario, shut down Orbiter, and then fire it back up and try to load the scenario. It crashes during the DLL load step during boot up. For example:

If you name your BCRS2's in the following manner:
BCRS2-M01-01a
BCRS2-M01-01b
BCRS2-M01-01c
BCRS2-M01-01d
BCRS2-M01-02a
BCRS2-M01-02b
BCRS2-M01-02c
BCRS2-M01-02d
...
BCRS2-M01-27a
BCRS2-M01-27b
BCRS2-M01-27c
BCRS2-M01-27d
BCRS2-M01-28a
BCRS2-M01-28b
BCRS2-M01-28c
BCRS2-M01-28d

Then save the scenario and exit Orbiter. When you start up Orbiter again and load the scenario it crashes. However, if you change the last quad of BCRS2s to:

BCRS2_M01-28aa
BCRS2_M01-28ba
BCRS2_M01-28ca
BCRS2_M01-28da

OR

BCRS2-M01a-28a
BCRS2-M01a-28b
BCRS2-M01a-28c
BCRS2-M01a-28d

And continue along those naming convention lines for the next 112 BCRS2s it works just fine.

As a work around, I fly each of my construction missions, save it, then immediately try to reload it. If it fails, I figure out a new naming convention that works, then adjust all the downstream missions to use it. I'm up to mission 164.....

Dantassii
HUMONGOUS IMS shipbuilder