Example: I'm submitting my first released example for public use - and all you blogreaders get it first.
http://www.savefile.com/files/241382This is, basically, an example dealing with "curved" reflections in 3d. This is normally not possible due to the incompatibility of surfaces with d3d native; however, by not actually entering d3d mode, one can render curved reflections using surfaces and sinewave-based drawing techniques. This example also includes some code to work around the depth-problems present in standard "3d in 2d" implementations by the use of depth-setting and position-based drawing.On that subject, GM7 or 7.1 SHOULD include the ability to use surfaces and d3d simultaneously. I don't care how it's done - just make it happen. It shouldn't be _that_ hard to do…MMO: Still working on it. I have created a main menu and an option to turn on a "low-detail" mode in which surface use is dramatically decreased. (esp. by removing water reflections) EotS: I made a deal with my brother regarding multiplayer testing, so I should be able to test it and get it in a working condition very soon.
cool
well im pretty sure i dont have video card errors omicron… 64 MB is enough right?
…uh… if you are playing a game from 1999, maybe. Probably not for this, though.
Thanks for making my job easier, now I know I can accept this right away ^_^
64D has a file uploader with a Download Counter just like Savefile, except there are no ads. Just click the Down arrow and copy the link it provides.
The screenshot looks really nice. The exampleis kind of wierd though… inverted directional keys and the effect doesn't do half of reflection.Probably just my computer being retarded again.
If you don't see the entire reflection, it's due to a relatively common error regarding surfaces that I *cannot* reproduce.
Hmh… I don't understand why so many people are having errors. I can't fix what I can't replicate.
Using surfaces with D3D while not actually initiating D3D is risky business, so while the errors people are having is unfortunate, it's not really unexpected.
Released fix in example topic.