For information and discussion about Oolite.
https://bb.oolite.space/
Yeah this bit:El Viejo wrote:In that log... is Oolite looking for a Viper player? Que?
Code: Select all
[shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "griff_normalmapped_viper_player" does not have a corresponding shipdata.plist entry, ignoring. See, now that's why you have your own ship set to a Griff_Cobby or something, so you can switch to an external view for a quick shot..DaddyHoggy wrote:Oolite coped very nicely - the only thing I was disappointed about was that none of the nice ships showed up in the brief time I had.
the first few tests of the normal mapped griff viper oxp had a player flyable version in it, it made it easier to test the ship by flying it around and looking at it using the external camera views, at some point it looks like i might have put out a version of the oxp with the player viper not completely removed from the shipdata.plist, which DH downloaded, the current version of the oxp won't have this bug (it'll probably have lots of new onesEl Viejo wrote:In that log... is Oolite looking for a Viper player? Que?
)If I recall, I think DH also uses the individual ship oxp's, rather than the all-in-one pack. Do you update all of those as well, when you find a bug, Griff?Griff wrote:the first few tests of the normal mapped griff viper oxp had a player flyable version in it, it made it easier to test the ship by flying it around and looking at it using the external camera views, at some point it looks like i might have put out a version of the oxp with the player viper not completely removed from the shipdata.plist, which DH downloaded, the current version of the oxp won't have this bug (it'll probably have lots of new onesEl Viejo wrote:In that log... is Oolite looking for a Viper player? Que?
I'd already downloaded most of the individual ships when the pack came out so I've stuck with that - however once the pack is finalised - I'll switch.Diziet Sma wrote:If I recall, I think DH also uses the individual ship oxp's, rather than the all-in-one pack. Do you update all of those as well, when you find a bug, Griff?Griff wrote:the first few tests of the normal mapped griff viper oxp had a player flyable version in it, it made it easier to test the ship by flying it around and looking at it using the external camera views, at some point it looks like i might have put out a version of the oxp with the player viper not completely removed from the shipdata.plist, which DH downloaded, the current version of the oxp won't have this bug (it'll probably have lots of new onesEl Viejo wrote:In that log... is Oolite looking for a Viper player? Que?
i try to yes, but not always successfully! i get easily confused about what files to copy where and what to overwrite between the individual oxps and the all-in-1 - it doesn't help that my oolite workstuff folder is a giant collection of folders & files all called 'THIS', or 'THISNEWER', 'THISHJDHKD' and variations thereofDiziet Sma wrote:If I recall, I think DH also uses the individual ship oxp's, rather than the all-in-one pack. Do you update all of those as well, when you find a bug, Griff?
You need a system, sir.. 