help, transparent textures and graphics errors: (

[Killik]

I leave a picture for you to understand that I can do thanks


http://www.uploadfilesystem.com/thumbs/09/09/18/tn_FfU03107.jpg

 

[robert kundrat]

I leave a picture for you to understand that I can do thanks

I think it is an ATI card compatibility problem.

1. Disable Hardware rendering in your editor,
2. save table,
3.close table,
4. reopen table again,
5. play.
I hope it will help.:)

 

[faralos]

why is it with me I must do the exact opposite? I must check hardware rendering, save the table exit vp9. Then reopen vp9 and reload and open the table again and every time I place an object into a table I build it UNchecks that box all by itself so the next time I go to play the table I get no ball, flippers, sometimes that "cannot create...surface"

 

[sleepy]

I'm not sure about this, but when I use VP 9.02 and open Eula's version of Frontier I get no visible flippers. When I check the Flipper settings under Options > Colors and Formatting > both the Rubber Offset Height and Rubber Width have very strange values which are not equal for both flippers. The RightFlipper has a Rubber Offset Height of, get this, 1144472790
and a Rubber Width of 1138501416 and the LeftFlipper has a Rubber Offset Height of 1040644315 and a Rubber Width of 0 (zero).

Obviously, the vp.exe is doing something very strange here. It is finding no values for these settings because the table is older than the existence of these settings, and then the .exe is asserting these unusual values from within the .exe. The values are out of bounds causing my ATI to ignore the rendering. The flippers are still physically operational. They're only invisible. When I set these values to 0 (zero) or a reasonable integer, the flippers render properly.

The .exe needs to assert a set of default values for settings when none are present in the table script, but the size and irregularity of the values being asserted by the .exe on the Frontier table seems to indicate that there is a memory leak in progress, possibly if there are no default values assigned in the .exe if and when they are absent in the table script.

 

[sleepy]

I forgot. Saving the table will screw it up as the .exe is asserting these wrong flipper values in the text areas of the Options, so when you Save, you also save these wrong values.

 

[destruk]

Sleepy, if you stick values into the flipper options that will render - like 0/8/34, then the flippers will be fine. It isn't a memory leak - it's simply an improperly initialized variable as those options don't exist in a vp8 table. You notice on any version of vp, sometimes the 'uservalue' field of an object will also have enormously ludicrous values stuck in there by default - another improperly initialized variable.

 

[sleepy]

Can missing variable values be asserted by the .exe by default?
It couldn't hurt.

 

[destruk]

Thing is, they should be, but they aren't right now. I don't see how it could be difficult to correct.