Spacecraft Soyuz 7K for Orbiter 2016

[Mr. Residuals]

I don’t have autofcs installed on Orbiter 2016. The scenarios load for me if I remove the vesselbuilder spacecraft from the launch scenario, or if I remove it as a payload. It has something to do with how vesselbuilder interacts with igel’s most recent build of Soyuz v1.3. I tried redownloading and reinstalling both, as well as making sure I had the updated missions file from Soyuz 7K installed, and each scenario crashes before fully loading.

Same with me, after I removed autofcs

 

[1987VCRProductions]

Tomorrow I’ll set up clean installation of Orbiter 2016 and try again to see if I can get it to work.

 

[1987VCRProductions]

I tried again on a clean installation of Orbiter 2016 and it didn't work.

 

[Luca]

I also tried with a the last beta version of Orbiter but the result is the same, it did'nt work.

 

[Mr. Residuals]

Okay, so I just installed all the ASTP Patches and for the Apollo docking port I get htis.

 

[Mr. Residuals]

Okay, so I just installed all the ASTP Patches and for the Apollo docking port I get htis. View attachment 26071

The Docking Module is off centered.

 

[MarkWatney2015]

I think I found out one of (hopefully not) many causes why launch scenarios does not load.

In the Soyuz launch scenarios (space station missions), the Salyut stations are still configured as SC3/4 vessels instead of VB (this was before animations were implemented and converted to VB), which I forgot to update them all. Haven't tested out solo missions and early non-Salyut missions yet however

In the Proton launch scenarios, I'm not sure what causes the problems (yet)...

Can you specify which scenario you all opened and failed to load (e.g Soyuz 11, Soyuz 18, Cosmos 638, etc.)? Thanks

 

[Luca]

Are there any news about the launch scenario problem?

 

[MarkWatney2015]

Sorry for not bringing any new updates. Real life currently taking a toll of my time, especially now that I need to pass all my requirements for the coming end of my 2nd-year semester. Once it's all done, I could continue working on this

 

[GEMINIDUDE44]

hello ! i have a problem with the soyuz 7k series addon on my Orbiter 2016 when i start a scenario the soyuz doesn't appear

 

[N_Molson]

Hello, please post the content of your Orbiter.log file so what we can tell you what is going on

 

[GEMINIDUDE44]

Well now i have this sort of glitch :

 

[Arvil]

Now, that was just weird.

 

[MarkWatney2015]

Well now i have this sort of glitch :

Hello, just dropping by the Forum....interesting launch bug on the rocket itself. This might be caused by a plugin module conflicting with the programming of the Soyuz rocket addon.

I'm suspecting Attachment Manager, however the said plugin causes the Soyuz to explode on the pad itself....

 

[GEMINIDUDE44]

Hello, just dropping by the Forum....interesting launch bug on the rocket itself. This might be caused by a plugin module conflicting with the programming of the Soyuz rocket addon.

I'm suspecting Attachment Manager, however the said plugin causes the Soyuz to explode on the pad itself....

Hi ! I was wondering to know how to fix it ? Nice Mod Btw !

 

[MarkWatney2015]

Thanks! I'm speculating one of the plugin modules found on the Modules tab on the Orbiter Launchpad just before you start any of the scenarios (the settings where you could activate TransX, OrbiterSound, ScenarioEditor, etc.) are causing the problem.

If you have Attachment Manager installed and activated, deactivate it first, but like I said it only causes the Soyuz rocket to explode on the pad and (may) not be the one causing it. If not, randomly deactivate any of the plugin modules before you start any launch scenario.

If the bug still occurs, you can ask help to the author of the Soyuz rocket, igel, by posting it here

 

[GEMINIDUDE44]

Thanks! I'm speculating one of the plugin modules found on the Modules tab on the Orbiter Launchpad just before you start any of the scenarios (the settings where you could activate TransX, OrbiterSound, ScenarioEditor, etc.) are causing the problem.

If you have Attachment Manager installed and activated, deactivate it first, but like I said it only causes the Soyuz rocket to explode on the pad and (may) not be the one causing it. If not, randomly deactivate any of the plugin modules before you start any launch scenario.

If the bug still occurs, you can ask help to the author of the Soyuz rocket, igel, by posting it here

how can i deactivate the attachment manager ? i cannot find it

 

[kuddel]

Any plugin that needs the symbolic link in "/Modules/Server/", maybe?
Creating that link can be easily done in the "D3D9Client Advanced Setup" with the "Create symbolic links" Button at the bottom.

 

[MarkWatney2015]

how can i deactivate the attachment manager ? i cannot find it

Don't worry, that means you don't have this mod installed. Usually when this is activated, the Soyuz rocket explodes while on the pad once it ignites its engines (or in the case of Multistage2015 vessels, they ascend into space in an instant for no reason at all).

 

[GEMINIDUDE44]

Don't worry, that means you don't have this mod installed. Usually when this is activated, the Soyuz rocket explodes while on the pad once it ignites its engines (or in the case of Multistage2015 vessels, they ascend into space in an instant for no reason at all).

Well it still doesn't work but it explode during the liftoff is there other way to fix it ? it is maybe the D3D9 configuration or the Orbiter Setting Configuration that makes those glitches