Referring to my issue here...
http://orbiter-forum.com/showthread.php?t=2539
I can get every ship in my "ultimate" scenario with Ummu working properly all around, but when I add the Exploreur class Ocean, Ummu locks up my comp.
I know the ship isnt the problem, as I have run many tests adding and subtracting various vessels from the scenario while testing ummu....
the issue is that ummu appears to have a ship cap, and the Exploreur class Ocean automatically spawns its surface vessel, three probes, and its fuel tanks every time I load the scenario.... which inevitably leads to me having too many ships for ummu to work properly.
Does anyone know if theres a way to force the Exploreur class Ocean NOT to spawn its probes on scenario load? (i've tested using scenario editor to delete the probes after load and Ummu works great...but this is a step I dont want to have to repeat every time I load)
Thanks for any help!
http://orbiter-forum.com/showthread.php?t=2539
I can get every ship in my "ultimate" scenario with Ummu working properly all around, but when I add the Exploreur class Ocean, Ummu locks up my comp.
I know the ship isnt the problem, as I have run many tests adding and subtracting various vessels from the scenario while testing ummu....
the issue is that ummu appears to have a ship cap, and the Exploreur class Ocean automatically spawns its surface vessel, three probes, and its fuel tanks every time I load the scenario.... which inevitably leads to me having too many ships for ummu to work properly.
Does anyone know if theres a way to force the Exploreur class Ocean NOT to spawn its probes on scenario load? (i've tested using scenario editor to delete the probes after load and Ummu works great...but this is a step I dont want to have to repeat every time I load)
Thanks for any help!
