Originally Posted by
gecko
So what results do you get when running the combination I suggested? Using the main RSM files from the Mk.II but overwriting the SpitMkII subfolder with the one from the Mk.V package I expect you would keep the stability of the Mk.V, but have it start more consistently like the Mk.II. But to be honest, all of the loading failures and CTDs are way more than what I've encountered with either package.
I'm happy to hear the CTDs are gone on the Mk.V. I put a fair amount of work into removing potential issues (even though I wasn't having CTDs, there where some aspects of the code which could allow them) so I'm glad that at least has paid off.
The prop changing position in the UI (as well as the cockpit door being open and the elevators drooping) are all indications that the initializer script is being loaded. If it correct to presume that if you see those things in the UI that the RSM launches successfully when you start the mission, or is that not always the case?
Bookmarks