[Lord Platin]

Hi everybody,
I recently started playing FS2 again and got the ShivanSpS-pack, upgraded it all the way as mentioned in his thread.
Everything was fine and I started playing... And after I restarted a mission I got the following:

I even updated to 3.6.9-RC3 (of course I also used the mediavp-patches provided there) but nothing changed. The first time I did a mission it worked, the second time it started showing me those weird yellow things.
My flags are:
-mod Fs1_port_3,mediavps -spec -glow -env -jpgtga -mipmap -nomotiondebris -2d_poof -missile_lighting -dualscanlines -targetinfo -orbradar -rearm_timer -3dwarp -warp_flash -snd_preload  -ambient_factor 0.85 -spec_exp 11 -spec_point 0.6 -spec_static 0.8 -spec_tube 0.4

So it's not really a problem keeping me from playing fs2 but it's kinda annoying and shouldn't stay in RC-versions

I have an ATI graphics card with the latest Omega drivers. And it's OGL


Lord Platin

[Colonol Dekker]

Death by Frazzles !!!!!!

[Wanderer]

Disable env mapping.

[taylor]

The env bug should hopefully be fixed in RC3 actually.  In any case, try the -disable_fbo option and see if that helps any.  If it is still the env bug then that might fix the problem without actually disabling env.

[Lord Platin]

Disabling env worked, this time I'll try -disable_fbo

[Colonol Dekker]

Almost forgot.



Blah Blah, hands, blah blah, Flamethrowers,
blah, exits left and right, blah enjoy your stay

[pecenipicek]

Almost forgot.



Blah Blah, hands, blah blah, Flamethrowers,
blah, exits left and right, blah enjoy your stay

Blah blah blah, no napalm only water. holy or otherwise, blah blah, hyperintelligent shade of blue opening the plasma gun compartmetn, blah blah blah blah blah

[Lord Platin]

-disable_fbo worked as well, so it's probably the mentioned env bug... whatever fbo is

[Colonol Dekker]

Frickin Blocky Orange (things?)
 

[Lord Platin]

I'd say it's yellow, but you never know... maybe it's some sort of... hyperintelligent shade of blue that is too intelligent to be seen as blue?

[Herra Tohtori]

All Hail Interplanetary Constructor race!

The Vogons have arrived!

[taylor]

-disable_fbo worked as well, so it's probably the mentioned env bug... whatever fbo is

It's not an env bug, it's a render-to-texture bug.  Well, that's not totally accurate either, it's the fact that ATI drivers suck.  That's the problem.

-disable_fbo just disables render-to-texture, that way you can still use env with the default envmap or a mission specified envmap.  It may not match the actual mission you are in (in the case of the default envmap) but you'll still get the improved lighting and some reflections at least.

[Turambar]

btw, could you instruct me on how Render-to-Texture works?

due to BTRL business, i think me and render-to-texture are going to have to be very good friends, and i'd love it if you could introduce us.

[WMCoolmon]

The basic method is

Code: [Select]

--Get the ship handle
ship = mn.getShipByName("Ship name")

--Get texture handle
tex = gr.loadTexture("newtexture")

--Swap the old texture with the new one with texture replacement
ship.Textures["oldtexture"] = tex
Doing it with a RTT-generated texture is a bit more complex, but uses the same basic method.

Code: [Select]

--Get the ship handle
ship = mn.getShipByName("Ship name")

--Create texture, if needed, and draw to it.
if not tex then
   tex = gr.createTexture(512, 512, "Dynamic")
end

--Set drawing target to the new texture
gr.setTarget(tex)

--Set color to yellow and draw "moocow" on the new texture
gr.setColor(255, 255, 0)
gr.drawString("Moocow", 0, 0)

--Reset render target
gr.setTarget()

--Swap the textures
ship.Textures["oldtexture"] = tex