OFSS II - Issues, problems and troubleshooting

[ky]

That doesn't sound right.Have you both recently installed the d3d9 graphics client?

 

[PhantomCruiser]

No, I'm not using any graphics client. Just the plain ol' 'stock' Orbiter.
There may be an underlying graphics related reason for the glitch though. I just came upon this as a quick fix. I'd originally thought this was a crewed Dragon, because I knew we still had the cargo version on station.
I'll keep troubleshooting, but we're A-OK to get past our roadblock here. It'd be nice to sort it out though.

 

[IronRain]

I'm getting the same. I went back and re-flew earlier Dragon missions and there was no problem or conflicts (and no disappearing Dragon).
BRB, I got an idea...

OK, I think I've got it. Delete the Dragon (cargo) that is currently docked to Neesys. It would appear that you can't have 2 Dragons of the same make/model in the same scenario, or at least not in the way presented here... At least deleting the cargo Dragon allowed this particular flight to work out anyway.

I'm updating the "bonus mission" to not only do a flyaround with the PTV (while Endeavour is on station), but to deorbit the Dragon cargo as well (maybe adding to the down-mass that Endeavour is bringing home perhaps? Anyway, this way the scenario should work.

Thanks, this worked. I think this is a problem on the Dragon's side? Not much we can do about it right?

 

[PhantomCruiser]

I think this is a problem on the Dragon's side?

Quite possibly, I'm going to go and peruse the Dragon development thread to see if anyone has had a similar issue. If nothing else I'll PM Glider to see if it's a known issue. :thumbup:

Nice screenshots BTW! And like the narrative, I heard Miles O'Brien's voice while reading it.

 

[Glider]

I think this is a problem on the Dragon's side?

Yes, this problem is because of Dragon. ( The reason: functions for adding thrusters and meshes were in clbkPostStep and was controlled by a static bool variable that is the same for every Dragon in a scenario, so when first Dragon loads it's meshes and changes that variable, all other Dragons can't add thrusters and meshes anymore ). There are no problems with many Dragons in the new version that I hope to finish during the next 1-2 weeks.

 

[C3PO]

It should be fairly easy to make a cfg version of dragon to use for the "inactive" ones in a scenario. Just remember to rename it.