Oolite Bulletins

Help! I'm stuck on some maths!
First, a bit of background:
The "tradeInFactor" uniform is an integer with a value between 75 - 100.
I've got it set up as a shader uniform called 'TradeFactor' in my shipdata.plist like this and in the fragment shader like this This looks OK, there's no errors in the oolite log.
Where i'm stuck is trying to convert this integer to a floating point number in my shader, and rescale it so that '75' now equals 0.0 and '100' equals 1.0 (i'll use the floating point number to power the amount of grunge to add to the ship)

I've got this in my fragment shader code: sorry about the confusingly named variables!

This bit of code seems to work OK in rendermonkey, i can manipulate the TradeFactor int value and the grunge effect only seems to happen when it's between 75-100, with 75 being no grunge effect and 100 being max grunge effect

The problem, is when i look at the ship in game it's already looking pretty beaten up like the int value is already at 90 or so

i found this in the savegame but changing that to diffrerent values, saving the file, starting oolite and loading in the savegame file doesn't seem to make any difference - the ship is always at the same level of beatenup-ness, what have i got wrong? - it's the sums isn't

I would think: (x - 75) / 25.

Explanation: range[75-100] - 75 = range[0-25]
range[0-25]/25 = range[0-1]

So (range[75-10] - 75) / 25 = range[0-1]

Edit: what you did wrong is thinking you divided by 100, and you had a range of [0-0.25] when you had in fact a range of [0-25], so multiplying by 4 gave a range of [0-100].

This grunge factor of 0.0 - does that mean no grunge or maximum grunge? If it means no grunge - which seems the obvious way round to do it - then you're trying to give a knackered ship with a trade in factor if 75 a nice pristine hull!

So I would say (100 - tradeInFactor)/25 if 0.0 means no grunge, or as Day says if it's maximum grunge.

Yup ^^

impressive work Griff.

Updated the griff_station_bundle oxp to version 1.2.1 - now includes Spara's bugfix mentioned a few posts above, Thanks for fixing this oxp Spara

Thanks also for the maths help Day and kanthoney, i did have it the wrong way around in my brain i think, for some reason i thought TradeinFactor of a 100 was the ship at it's most worn out, rather than at its most pristine!
I've sorted out new shaders for the following OXPs and uploaded them to box.com - for some reason the version numbers there were really messed up, these are definitely the latest versions now, even if the numbers on some of them seem to have gone backwards - i think the uploaded wolf-MKII.zip file was v1.5 or something, whilst it was v1.4 on my pc and in the file comments on box.com anyway, find them here https://app.box.com/shared/rpkms25cc9 The player versions of these ships should show signs of wear and tear over time as well as all the NPC versions will have a random amount a grunge on them.
I haven't played long enough to see if the player ship will wear out, i hope it does - does anyone know if there's a console command to modify the player ship tradeInFactor value whilst in game - editing the number in the save game doesn't seem to have any effect, at least not on the shader

A pretty good reason to switch to a Wolf MK II for a while, is that - thanks!

awesome, thanks for testing - let me know if it the ship gets more grungy over time - it should start looking dusty, then the colours will start to turn greyish before some paint starts chipping off. it's all powered from the specular intensity map so some ships work better than others depending on how careful I was creating that specmap, the core shipset don't really look good at all with this effect so i'll have to tinker about with those to see if I can get it working

Wow, that's a really impressive use of the system to simulate wear-n'-tear!

Great Griff. I believe I have suggested it before, but now that the station bundle is quite finished (or is it?), how about putting it to the manager?

Griff wrote:

does anyone know if there's a console command to modify the player ship tradeInFactor value whilst in game - editing the number in the save game doesn't seem to have any effect, at least not on the shader

You are looking for player.ship.serviceLevel and it looks like it works. Here is the Wolf MkII at various stages of wear and tear:
Brand new:


80%:


77%:


75%:

Same exercise as before, Griffin MkI:
Brand new:


85%:


80%:


75%:

Yay! That's awesome. Thanks for testing that out a_c

@spara - that's a good idea. I've got all the logins and stuff, just need to have a look at Dizzy's excellent oxz tutorial thread and see if I can follow along.
Just looking at the station bundle oxp at the moment, I think I can take out nearly all of the Model files now, they're already in the standard game (apart from the Ico hull, looks like I've rearranged some of the UV maps at some point and the 'oolite_ico_hull.dat' causes texture seams with the bundle oxp)

Griff wrote:

...I think I can take out nearly all of the Model files now, they're already in the standard game...

I would say that it's better to include the models to the OXP and possibly avoid conflicts later. Size wise the models are only a small fraction of the OXP.

That seems sensible
OK, I think this is done, the station bundle should now be up on the manager!