Jededia..Did you kill the TD feature? I mean the one that causes the RCS to jump around (as mentioned previously in this thread).
The other day I discovered that using the Pursuit MFD with IMS finished vessel (from a restatred scenario) I can guarentee a CTD. Further investigations showed that I indeed clould start pursuit but it was when I activated the RCS in the engineer screen that the CTD occured. Tested both ways.. i.e.:
- Startsituation with Pursuit active > GO RCS > CTD.
- Startsituation with RCS active > GO Pursuite > CTD.
By the way...Pursuit MFD is one the the "trickier" MFDs when it comes to CTD so I dont think that IMS perhaps is entirely to blame. But just to let you know...especially with the RCS take on it.
And...me like the Scripted (auto) integration feature.
---------- Post added at 04:10 AM ---------- Previous post was at 02:10 AM ----------
OK...Gentlemen...brace yourself a little bit because this D3D9 might be a little more tricky than that
Based on Jededias and Dantassii findings that there might be a finite limit on the number of modules that D3D9 could handle I decided to investigate a little. To cut a long story short its indicated that D3D9 client might be sensitive to vessel names. I.e a two cfg files with the same contents but with different filenames > one causes a CTD the other doesnt.
To replicate try this:
Start a clean scenario (in D3D9 enviroment) (I used this one):
Code:
BEGIN_DESC
END_DESC
BEGIN_ENVIRONMENT
System Sol
Date MJD 53125.4721088296
END_ENVIRONMENT
BEGIN_FOCUS
Ship DG
END_FOCUS
BEGIN_CAMERA
TARGET DG
MODE Extern
POS 2.99 -118.47 -20.51
TRACKMODE TargetRelative
FOV 60.00
END_CAMERA
BEGIN_HUD
TYPE Surface
END_HUD
BEGIN_SHIPS
DG:Deltaglider
STATUS Orbiting Earth
RPOS 7006285.40 0.00 159952.22
RVEL -172.130 -0.000 7539.721
AROT 0.00 0.00 0.00
AFCMODE 7
PRPLEVEL 0:1.000000 1:1.000000
NAVFREQ 0 0 0 0
XPDR 0
AAP 0:0 0:0 0:0
END
END_SHIPS
BEGIN_ExtMFD
END
END
Start Scenedit and start to add a vessel and give it a name.
Using the STD IMS path layeout for SBB41rev2 go to connectionparts (my path is orbiterpart\Config\Vessels\IMS\SBB41BRev2\Connection_Parts) and add this module "BT302_LargeTrussToSmallTruss_Short". I get a CTD at this point. If I add it manually via txt edit I also get a CTD.
Then I changed the filename of the cfg file to:"D3-test-BT302" so the scenario now looks like this:
Code:
BEGIN_DESC
Contains the latest simulation state.
END_DESC
BEGIN_ENVIRONMENT
System Sol
Date MJD 53125.4735081022
END_ENVIRONMENT
BEGIN_FOCUS
Ship DG
END_FOCUS
BEGIN_CAMERA
TARGET 45
MODE Extern
POS 2.99 -82.09 -16.07
TRACKMODE TargetRelative
FOV 60.00
END_CAMERA
BEGIN_HUD
TYPE Surface
END_HUD
BEGIN_SHIPS
DG:Deltaglider
STATUS Orbiting Earth
RPOS 6926321.84 -0.00 1067561.73
RVEL -1148.841 -0.000 7453.670
AROT 0.00 0.00 0.00
AFCMODE 7
PRPLEVEL 0:1.000000 1:1.000000
NAVFREQ 0 0 0 0
XPDR 0
AAP 0:0 0:0 0:0
END
test:IMS\SBB41BRev2\Connection_Parts\D3-test-BT302
STATUS Orbiting Earth
RPOS 6985476.49 -0.00 562794.89
RVEL -605.645 -0.000 7517.327
AROT 0.00 -0.00 0.00
AFCMODE 7
NAVFREQ 0 0
END
END_SHIPS
BEGIN_ExtMFD
END
END
No CTD occurs now.
This CTD is also is also path sensitive because adding the same cfg file from sbb41(rev1) where the relative filepath is one step shorter also does not cause a CTD. Have checked...my symbolic links works
i.e. the files are updated in modules\server path.
The goos news is that there is a work around...apparently changing to shorter
paths and file names does have an effect on the D3D9 client. Maybe Dantasii can get the humoungous ship up and running in D3D9 with some carefull editing.
ps. the reason why this came along is that I have scenarios with +600 docked modules that run OK in D3D9 so it might not be the number of files but more name and/or path related