The curse of the shiny blue ships strikes again!
Posted: Sat Nov 13, 2010 2:45 am
I'm a bit confused about shaders and things...
Does Oolite sometimes take a while to load things, while running?
I've just downloaded the neolite core, companion and wolfies oxps (and most of the other oxps from Simon B's site, but haven't started installing them yet!) and am getting some odd effects.
Just adding the companion and wolfies oxps runs with no problems. Neither of these use shaders.
Just adding the core set results in a blue neolite cobby at start up, and all the neolite ships are blue. Also, so are ADCK's Eagles, which also use the neolite shaders (which aren't in the eagles oxp, but are in the neolite core)
Running with all 3 installed results in a blue cobby on start up, and blue neolite ships initially, which after a few seconds sort themselves out and are properly textured.
Note that they are the same adder, just 6 seconds apart.
Also, the eagles now have glowing engines. So presumably they work.
What's more, selecting "begin new game" from the menu now results in seeing the proper neo-cobby.
If this has something to do with load order, this is the order they load in:
neolite.oxp
neolite-wolfies.oxp
adcks_eagles_v1.1.oxp
neolite-companion.oxp
(with, of course, all my other oxps amongst them as well...)
[It occurs to me that the hud always takes a while to load as well. As you can see from the screenshots, upon startup it is always the default hud that shows. The MilHud only seems to start running once I leave the station. Although, as you can see from above, if I select the option to start a new game from within an already running game, I get the MilHud...]
So, if I run all three, then the shaders in core neolite appear to work, despite there being no shaders in the other two as far as I can tell. Which means that I do not necessarily have a functional problem as such, but I'd like to know what the underlying cause of this is. I've had similar problems with ADCK's Behemoths, which caused Griffs ships (only some of them!) to turn this unnatural colour, and the same thing with shady_sungs (though I can't remember which ships were turning blue, only that some were and it stopped when I took them out). If anyone can work out why in this case the problem seems to resolve itself, perhaps I can do something about the others...
I'm running shader mode "Simple" (the best my computer can do), and there are no errors that show up in the log file (apart from the eagles wanting the neolite shaders, but that's not the issue here).
Congratulations if you managed to get through all of that! Have a well earned round of applause!
Does Oolite sometimes take a while to load things, while running?
I've just downloaded the neolite core, companion and wolfies oxps (and most of the other oxps from Simon B's site, but haven't started installing them yet!) and am getting some odd effects.
Just adding the companion and wolfies oxps runs with no problems. Neither of these use shaders.
Just adding the core set results in a blue neolite cobby at start up, and all the neolite ships are blue. Also, so are ADCK's Eagles, which also use the neolite shaders (which aren't in the eagles oxp, but are in the neolite core)
Running with all 3 installed results in a blue cobby on start up, and blue neolite ships initially, which after a few seconds sort themselves out and are properly textured.
Note that they are the same adder, just 6 seconds apart.
Also, the eagles now have glowing engines. So presumably they work.
What's more, selecting "begin new game" from the menu now results in seeing the proper neo-cobby.
If this has something to do with load order, this is the order they load in:
neolite.oxp
neolite-wolfies.oxp
adcks_eagles_v1.1.oxp
neolite-companion.oxp
(with, of course, all my other oxps amongst them as well...)
[It occurs to me that the hud always takes a while to load as well. As you can see from the screenshots, upon startup it is always the default hud that shows. The MilHud only seems to start running once I leave the station. Although, as you can see from above, if I select the option to start a new game from within an already running game, I get the MilHud...]
So, if I run all three, then the shaders in core neolite appear to work, despite there being no shaders in the other two as far as I can tell. Which means that I do not necessarily have a functional problem as such, but I'd like to know what the underlying cause of this is. I've had similar problems with ADCK's Behemoths, which caused Griffs ships (only some of them!) to turn this unnatural colour, and the same thing with shady_sungs (though I can't remember which ships were turning blue, only that some were and it stopped when I took them out). If anyone can work out why in this case the problem seems to resolve itself, perhaps I can do something about the others...
I'm running shader mode "Simple" (the best my computer can do), and there are no errors that show up in the log file (apart from the eagles wanting the neolite shaders, but that's not the issue here).
Congratulations if you managed to get through all of that! Have a well earned round of applause!