i seriously need to scale down the 1024x1024 texture and merge some of the effects maps together, i totally didn't realise we could use the alpha channel as well *studies photoshop help files to find out how to use the alphachanel* i think i might remove the specular exponent maps and just give it a fixed value in the shader, i'm not really using it much and it's taking up space.
i'll change the pow calculation to the other example you posted in the shaders outpost thread ahruman, the quadratic curve, you did warn that the pow one was expensive to use, i forgot to change it when saving out the final fragment shaders from rendermonkey.
Dohhhh, obviously!
The Grey Haired Commander has spoken!
OK so I'm a PC user - "you know whats scary? Out of billions of sperm I was the fastest"
From a shader perspective, an alpha channel is like any other channel. However, prior to 1.69 (or possibly 1.68), Oolite would premultiply textures by their alpha channels when loading them under OS X (I don’t know about other platforms). Also, prior to 1.69, the alpha channel was kinda-sorta used when rendering without shaders; it is now completely ignored. If you want an OXP to work without shaders in Oolite 1.68 and earlier, don’t use the alpha channel on the texture that’s used for non-shader rendering.
To complicate matters, GLSLEditorSample (which I use to edit and test shaders under OS X) also premultiplies textures when it loads them. This behaviour comes from Cocoa/OpenStep. It probably doesn’t happen in RenderMonkey, but it might.
here's a slightly less system demanding version of the ship http://www.box.net/shared/4rm3dqsclr 1.3MB
I've halved most of the texture map sizes and managed to merge a few of the maps together using the baffling alpha channel. Turrets should be working too with the ones on the back not upside down anymore.
Ahruman the "#ifdef OO_REDUCED_COMPLEXITY" around your shader pulse function, does it always choose the reduced complexity version at the moment? i'm convinced on my system that it does.
that's odd, the turrets should be working, they're not in the screen shot i posted a few posts back (the quaternions were giving me problems) but they should be in the version i put up for download... there was a problem with me not giving the turrets a 'thrust' value in their shipdata.plist, ahruman pointed out that this stopped them from being able to track targets but i thought i'd fixed that. there's no turrets on the front and underside of the ship so it can't get you if you hide there, try popping around the back and fire a few lasers into it's engines.
A look into Behemoth.oxp shows turrets usually have a thrust value of 1.
Cranking it to 1.5 might give them faster tracking - if it has an effect at all - but I suspect it'll make their gunnery skills fairly sloppy.
Running Oolite buttery smooth & rock stable w/ tons of eyecandy oxps on:
ASUS Prime X370-A
Ryzen 5 1500X
16GB DDR4 3200MHZ
128GB NVMe M.2 SSD (Boot drive)
1TB Hybrid HDD (For software and games)
EVGA GTX-1070 SC
1080P Samsung large screen monitor
Ahruman the "#ifdef OO_REDUCED_COMPLEXITY" around your shader pulse function, does it always choose the reduced complexity version at the moment? i'm convinced on my system that it does.
Currently OO_REDUCED_COMPLEXITY is never defined, so the reduced-complexity code is never used. It’s a planned future feature, like OO_LIGHT_0_FIX. :-)
Stupidly-high-poly-cobra-iii-mangleifification.oxp sneak peak
How's the pilot going to make Lavian TreeGrub smoothies when the food blender's mounted outside on the hull?
@Griff - just noticed the "blender" as A_C calls it - I'm afraid I'm going to have to report you to the authorities as it looks a lot like a classified project I used to work on - no seriously it does - can't tell you what though - otherwise I'd have to shoot you...
it's 2383 polys! I Haven't loaded the model into Oolite yet to see how it plays, hopefully it will be ok, otherwise i'll cut out a lot of the bevelled polys around edges of some of the shapes - i've put these in to see how they work with the lighting, i'm hoping they'll help oolite smooth out the lighting across the model really nicely
Good idea about the scale of the food blender, now you've pointed it out it's way too tall, funny how i hadn't noticed that before, i haven't started UV unwrapping that part of the model yet so it can be changed really easily
I do not believe that this thread justifies the title of "Ruining the classics" any more. Now it is more close to "Enchancing the classics"
This model is not only a remarkable ship but also a valid replacement for the original cobra
it's 2383 polys! I Haven't loaded the model into Oolite yet to see how it plays, hopefully it will be ok, otherwise i'll cut out a lot of the bevelled polys around edges of some of the shapes - i've put these in to see how they work with the lighting, i'm hoping they'll help oolite smooth out the lighting across the model really nicely
I think that some clever use of normal / parallax maps here could reduce the poly count requirements considerably, no?
