New Release Interplanetary Modular Spacecraft RC9

[PeterRoss]

Works for me:

I have removed all the non-IMS vessels from the scenario and it started well.

Try to remove everything between these strings:

BEGIN_SHIPS
...
Mir2:IMS\Command_Modules\BM201_CONTROL_MODULE

and check if it's working now. If it is, try to add vessels back one by one and this way you'll find the cause of a problem.
If the scenario isn't working anyway, try to disable all Orbiter modules except of Scenario Editor and then start it.
Please tell your results here.

And, one more thing: when posting a scenario, it's better to post it under CODE tag. Just paste your scenario into message window, select all its strings and click grey CODE button just above the message window, second to the left from a smile button. Like this:

BEGIN_DESC
MJD:70282 8 modules installed
END_DESC

BEGIN_ENVIRONMENT
System Sol
Date MJD 70282.0089478661
END_ENVIRONMENT

BEGIN_FOCUS
Ship Mir2
END_FOCUS

BEGIN_CAMERA
TARGET Mir2
MODE Cockpit
FOV 40.00
END_CAMERA

BEGIN_PANEL
END_PANEL

BEGIN_SHIPS
Mir2:IMS\Command_Modules\BM201_CONTROL_MODULE
STATUS Orbiting Earth
RPOS 5240490.36 -441.84 4649580.88
RVEL -5011.244 -1.856 5638.469
AROT 0.00 0.12 0.00
AFCMODE 7
PRPLEVEL 0:0.000002 1:0.000000 2:0.000001
NAVFREQ 0 0
COMMAND 0 0
MODULE Nodes\BN201_Big_Node 0,0,-7.276 0,1,0 1,0,0 0
MODULE Modules\BM101_Habitat 0,0,-14.5521 0,0,1 0,1,0 0
MODULE Modules\BM010_Habitat 4.5756,0,-7.276 -1,0,0 0,1,0 0
MODULE Modules\BM101_Habitat -7.2761,0,-7.276 1,0,0 0,-1,0 0
MODULE Truss_Parts\BT100_Truss 12.027,0,-7.2761 -1,0,0 0,1,0 0
MODULE Truss_Parts\BT100_Truss 22.1789,0,-7.276 -1,0,0 0,1,0 0
MODULE Power_Generation\BP101_Solar_panel 29.4019,-4.1071,-7.276 0,1,0 0,0,1 0
MODULE Life_Support\BG101_Lifesupport_Container 12.0268,2.3574,-7.276 -1,0,0 0,-1,0 0
TDPOINT 0,0,0 0,0,0 0,0,0
DELETEPOINT 2
ATTPOINT IM 0,2.2,-7.276 0,1,0 0,0,1
ATTPOINT IM 0,-2.2,-7.276 0,-1,0 0,0,1
ATTPOINT IM 0,0,-19.6281 0,0,-1 1,0,0
ATTPOINT IM -12.352,0,-7.2761 -1,0,0 0,0,1
ATTPOINT IM 12.0268,0,-6.187 0,0,1 -1,0,0
ATTPOINT IM 12.0268,0,-8.365 0,0,-1 -1,0,0
ATTPOINT IM 12.0268,-1.089,-7.276 0,-1,0 -1,0,0
ATTPOINT IM 22.1785,0,-6.187 0,0,1 -1,0,0
ATTPOINT IM 22.1785,0,-8.365 0,0,-1 -1,0,0
ATTPOINT IM 22.1785,1.089,-7.276 0,1,0 -1,0,0
ATTPOINT IM 22.1785,-1.089,-7.276 0,-1,0 -1,0,0
ATTPOINT IM 31.5495,0,-7.276 1,0,0 0,0,1
ATTPOINT IM 12.0264,3.6253,-7.276 0,1,0 -1,0,0
DELETEPORT 1
CONSTRUCTIONPORT 0,2.2,-7.276 0,1,0 0,0,1
CONSTRUCTIONPORT 0,-2.2,-7.276 0,-1,0 0,0,1
CONSTRUCTIONPORT 0,0,-19.6281 0,0,-1 1,0,0
CONSTRUCTIONPORT -12.352,0,-7.2761 -1,0,0 0,0,1
CONSTRUCTIONPORT 12.0268,0,-6.187 0,0,1 -1,0,0
CONSTRUCTIONPORT 12.0268,0,-8.365 0,0,-1 -1,0,0
CONSTRUCTIONPORT 12.0268,-1.089,-7.276 0,-1,0 -1,0,0
CONSTRUCTIONPORT 22.1785,0,-6.187 0,0,1 -1,0,0
CONSTRUCTIONPORT 22.1785,0,-8.365 0,0,-1 -1,0,0
CONSTRUCTIONPORT 22.1785,1.089,-7.276 0,1,0 -1,0,0
CONSTRUCTIONPORT 22.1785,-1.089,-7.276 0,-1,0 -1,0,0
CONSTRUCTIONPORT 29.4015,1.083,-7.276 0,1,0 0,0,1
CONSTRUCTIONPORT 31.5495,0,-7.276 1,0,0 0,0,1
CONSTRUCTIONPORT 12.0264,3.6253,-7.276 0,1,0 -1,0,0
EMPTYMASS 42500.000000
MASSCENTER 0.704484 0.145820 -7.179012
PMI 38.600000 42.600000 40.800000
ANIM 6 Power_Generation\BP101_Solar_panel 1 1
CONSUMABLES 68.0001 0.0001 0 260 0.0001 0 50.0001 0.0001 0
TEMPERATURES -1:298.07:383.01 1:298.07:383.01 2:298.02:334.37 3:298.03:334.36 6:330.45:330.00 7:298.00:298.01
HEATING -1
THGROUPLEVELS 0 0 0 0
CREW 9 0
ENERGY 990000000.000000
SOLARARRAY 6 1 0 0.249981 0.249981 0.166114 0.166114
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 1 0 2 -1 -1 -1 -1
MFC 1 0 6 0 0 10 -1
MFC 1 0 5 -1 -1 -1 -1
MFC 1 0 7 0 0 0 -1
END
END_SHIPS

 

[romanasul]

Alright I'm still getting a crash it says Fault Module name: IMS.dll
I deleted everything else from the scenario file and I disabled all modules except scenario editor and Direct3d9. Maybe something is wrong with my IMS install. I installed the newest RC6 plus the directx9 fix posted on the IMS page.

 

[PeterRoss]

Alright I'm still getting a crash it says Fault Module name: IMS.dll
I deleted everything else from the scenario file and I disabled all modules except scenario editor and Direct3d9. Maybe something is wrong with my IMS install. I installed the newest RC6 plus the directx9 fix posted on the IMS page.

Try to rebuild the vessel from scratch. For starters, spawn the Command Module and save, then load the scenario. If it works, continue building it.

You may also try to reload IMS package.

 

[romanasul]

It crashes even with just the command module. I reinstalled space station building blocks 4.0, 4.1, and swift ss followed by IMS and it still crashes. I just don't understand what the problem is. I'll continue to try to get it to work, thanks for your help.

 

[PeterRoss]

You could try it on vanilla Orbiter install.
Have you tried to run it under inline graphic client?

---------- Post added at 22:23 ---------- Previous post was at 19:25 ----------

I managed to reproduce your situation on vanilla Orbiter with IMS/SBB41/D3D9RC12 installed with D3D9 fix NOT installed. Please check if you installed it correctly.

 

[romanasul]

You could try it on vanilla Orbiter install.
Have you tried to run it under inline graphic client?

---------- Post added at 22:23 ---------- Previous post was at 19:25 ----------

I managed to reproduce your situation on vanilla Orbiter with IMS/SBB41/D3D9RC12 installed with D3D9 fix NOT installed. Please check if you installed it correctly.

Ok, I tried it on a fresh Orbiter install with Directx7 and I get the same crash. I noticed that someone else had the same problem on Page 75 on this thread. This might be related to something else although i'm not sure.

 

[Dantassii]

Ok, I tried it on a fresh Orbiter install with Directx7 and I get the same crash. I noticed that someone else had the same problem on Page 75 on this thread. This might be related to something else although i'm not sure.

If you are using the latest RC for IMS, you have to use the DirectX9 patch that was noted. I believe the current RC crashes in DX7 because they are incompatible with each other in the case of the stuff that IMS does with modules.

Dantassii
HUMONGOUS IMS shipbuilder

 

[romanasul]

I tried this, but it still crashes. Fresh Orbiter install/UCGO 2.5/D3D9/SBB4.0/SBB4.1/IMS/D3D9 compatibility patch

---------- Post added at 03:44 PM ---------- Previous post was at 03:36 PM ----------

Maybe I'm doing something wrong. I load up the BM201_CONTROL_MODULE, save the scenario and quit orbiter launchpad. I then load up Orbiter with the scenario and the game crashes saying IMS.dll is at fault.

 

[Dantassii]

I tried this, but it still crashes. Fresh Orbiter install/UCGO 2.5/D3D9/SBB4.0/SBB4.1/IMS/D3D9 compatibility patch

---------- Post added at 03:44 PM ---------- Previous post was at 03:36 PM ----------

Maybe I'm doing something wrong. I load up the BM201_CONTROL_MODULE, save the scenario and quit orbiter launchpad. I then load up Orbiter with the scenario and the game crashes saying IMS.dll is at fault.

You have to install the DirectX9 patch that is linked in the first page of this thread and then run Orbiter from it using the orbiterng.exe binary. Otherwise, you're either running DirectX7 or the original DirectX9, neither is compatible with IMS RC 6.

Or so I've been told.

Dantassii
HUMONGOUS IMS shipbuilder

 

[romanasul]

Yes, D3D9 doesn't work with Orbiter.exe so of course I run it with Orbiterng.exe. Maybe the problem is hardware related?

 

[Dantassii]

Yes, D3D9 doesn't work with Orbiter.exe so of course I run it with Orbiterng.exe. Maybe the problem is hardware related?

But you have to download and install the patched version of D3D9 that there is a link to at the front of this thread. If you are using the standard D3D9 add-on, it won't work.

Your comments don't mention installing the special, patched version of the D3D9 from this thread, so I am assuming that you are trying to use the standard D3D9 add-on and that's what is causing your problems.

Dantassii
HUMONGOUS IMS shipbuilder

 

[romanasul]

Sorry for not mentioning it, I am using the patched update. I usually find the solutions to problems quite fast but for this I have no idea.

---------- Post added at 07:53 PM ---------- Previous post was at 05:03 PM ----------

I have no idea what happened, but it seems to work now. I loaded the command module from the XR5 payload interface and now it seems to let me load it from the scenario editor without crashing upon re-load.

 

[PeterRoss]

I really can't tell what's wrong :shrug: RC6 is compatible with inline DX7 client, and even if the D3D9 fix is not onstalled it have to work.
Maybe Jedidia would tell something when he's around.

What's your hardware/OS?

---------- Post added at 07:27 ---------- Previous post was at 07:22 ----------

I have no idea what happened, but it seems to work now. I loaded the command module from the XR5 payload interface and now it seems to let me load it from the scenario editor without crashing upon re-load.

It's not very good, because the problem may appear again any moment. I call it gremlin, competent people call it memory leak, and it's a good indicator of something wrong, but it's very hard to find and fix.

 

[romanasul]

I really can't tell what's wrong :shrug: RC6 is compatible with inline DX7 client, and even if the D3D9 fix is not onstalled it have to work.
Maybe Jedidia would tell something when he's around.

What's your hardware/OS?

---------- Post added at 07:27 ---------- Previous post was at 07:22 ----------



It's not very good, because the problem may appear again any moment. I call it gremlin, competent people call it memory leak, and it's a good indicator of something wrong, but it's very hard to find and fix.

Well thank you to everyone for their help, I've been wanting to play with this for some time and now I can finally enjoy it.

 

[PeterRoss]

Well thank you to everyone for their help, I've been wanting to play with this for some time and now I can finally enjoy it.

Sure. If you have any questions about using IMS I'll try to help :tiphat:

 

[romanasul]

This is pretty unusual, I think the vessel name has something to do with the crashes I was experiencing. Lengthening the name of the command module seems to solve the crashes.

 

[PeterRoss]

This is pretty unusual, I think the vessel name has something to do with the crashes I was experiencing. Lengthening the name of the command module seems to solve the crashes.

I may be saying something stupid here, but in the ignorant way I see it the memory leak effects (if it is memory leak after all) should be different in different circumstances. I.e. if you change something, it may or may not cause unpredictable errors. Question is if the leaked data is overlapping some block of memory used by the program. In this sense changing the vessels' name lenght also MAY change the memory allocation for variables and stuff. It's still no panacea though.

Now guys more competent in coding can start laughing at my babbling.
:hide:

 

[Dantassii]

This is pretty unusual, I think the vessel name has something to do with the crashes I was experiencing. Lengthening the name of the command module seems to solve the crashes.

Ship names are not allowed to have spaces in them. This is a limitation of Orbiter.

Does your ship name that crashes have any spaces in it?

Dantassii
HUMONGOUS IMS shipbuilder

 

[BruceJohnJennerLawso]

Ship names are not allowed to have spaces in them. This is a limitation of Orbiter.

Does your ship name that crashes have any spaces in it?

Dantassii
HUMONGOUS IMS shipbuilder

I wish this were hard coded into the scenario editor. It would save the community so much grief in the long run.

 

[Dantassii]

I wish this were hard coded into the scenario editor. It would save the community so much grief in the long run.

What really annoys me is that bases are allowed to have spaces but spacecraft are not.

Dantassii
HUMONGOUS IMS Shipbuilder