happily it looks like the mistake is just in the 'addition' version of the oxp,
I've got the replacement version and it's in there, too. I even remember that I noticed it when working on the shipdata. But I first thought it was perhaps a deliberate change and then forgot to report it.
El Viejo wrote:
Where exactly, please? I can't find the damn line!
Oops! Apparently I did correct it after all. It was wrong in the original shipdata, but is correct in my overhauled shipdata. So obviously I must have corrected it.
Sorry for misremembering. (And the entry in question is griff_normalmapped_viper_interceptor_engines_gun.)
Oops! Apparently I did correct it after all. It was wrong in the original shipdata, but is correct in my overhauled shipdata. So obviously I must have corrected it.
Cool... I thought I was missing something (my brain).
Commander McLane wrote:
Sorry for misremembering. (And the entry in question is griff_normalmapped_viper_interceptor_engines_gun.)
Which in my shipdata.plist reads: "griff_normalmapped_viper_interceptor_engines_gun 0 0 0 1 0 0 0".
Further up in the plist I have: "forward_weapon_type" = "WEAPON_NONE";
Is that all correct?
I would advise stilts for the quagmires, and camels for the snowy hills
And any survivors, their debts I will certainly pay. There's always a way!
(And the entry in question is griff_normalmapped_viper_interceptor_engines_gun.)
Which in my shipdata.plist reads: "griff_normalmapped_viper_interceptor_engines_gun 0 0 0 1 0 0 0".
Further up in the plist I have: "forward_weapon_type" = "WEAPON_NONE";
Is that all correct?
Nope. What you're looking at is the subentities-key of the viper-interceptor entry. This points to the name of the entry which is to be used as a subentity (griff_normalmapped_viper_interceptor_engines_gun) together with the coordinates where this entry has to be put (0 0 0) and the orientation it has to be given (1 0 0 0). In order to find this entry you have to go up much further in the shipdata (at least if they're ordered alphabetically) and find the entry that looks like
@EV, it's line 7715 in the addition oxp, don't worry about the "weapon_none" line - this is because the gun and the engines on the viper are actually a seperate subentity to the main hull of the ship
edit: Ninja'd
Last edited by Griff on Thu Apr 19, 2012 11:34 am, edited 1 time in total.
Hi Griff, i'm using the latest trunk 1.77.0.4891 and i'm getting this invisible texture issue. When i transfer the save over to version 1.76 and exit the same station the textures are present and correct.
hmm, that missing texture is quite a large one - 2048x2048 pixels, i wonder if it's something to do with the work-in-progress shader sythesiser code that's part of the new features in trunk - there's a half size textures version of that station available in my folder in box that might work better, I'll have to grab a download of trunk from the nightlies, there's lots of exciting stuff going on in it as seen in various threads here on the forum
there's a half size textures version of that station available in my folder in box that might work better
I probably should've been a little more descriptive Griff. I was using the half size tex, i've since downloaded the full size and it works a charm, so i'll stick with that. I'll leave that little issue with the half size with you. It's the least i can do.
I can't play oolite without your textures Griff, they're all a beauty to behold, a bit like yourself no doubt!
...I can't play oolite without your textures Griff, they're all a beauty to behold, a bit like yourself no doubt!
Alas, i have a face like a sun baked trumble
Well, the odd half size texture thing might be something to do with them being re-scaled and saved in xnview, prehaps it did that interlace thing that some of the guys were chatting about the other day (something to do with interlacing and libpng), i'll grab a copy of the nightly build of trunk, put on my Miss Marple outfit and do some investigating