Triangles disappearing then reappearing
Obviously you can't get out of a fullscreen window using your mouse, the default way is to press Alt-F4 (at least under windows), but yeah if you run fullscreen then pressing escape to exit is a good plan.
Can't suggest anything more other than trying the things i did to see if it's the same problem or not!
Can't suggest anything more other than trying the things i did to see if it's the same problem or not!
JP I have news...
Thanks to the Quadtree Bitplane told me about in the "Tips for making an HOMM like game" (not the quadtree itself but that gave me an idea), I found why my map was disappearing.
I was adding my map as an Octree scene node, but if I use just addMeshSceneNode, it does not disappear anymore !
At least it is one issue solved, but maybe Hybrid should have a look at it ?
Thanks for trying to help JP
Thanks to the Quadtree Bitplane told me about in the "Tips for making an HOMM like game" (not the quadtree itself but that gave me an idea), I found why my map was disappearing.
I was adding my map as an Octree scene node, but if I use just addMeshSceneNode, it does not disappear anymore !
At least it is one issue solved, but maybe Hybrid should have a look at it ?
Thanks for trying to help JP
--
Lideln, France
Lideln, France
Yes I saw that it worked for you in fullscreen mode, so thats nice (but still strange that it does not work in windowed)
Indeed Im really happy that this issue is solved because it was getting on my nerves to see the map disappearing if I dared to move too much around the map
Things are getting better these days
Indeed Im really happy that this issue is solved because it was getting on my nerves to see the map disappearing if I dared to move too much around the map
Things are getting better these days
--
Lideln, France
Lideln, France
I did not get the same issue as JP.
For me, it was obviously the fault (but according to what criteria ?) of the OctreeSceneNode, because it works fine if I do not use it for the level (but I got this issue only with the level, not the objects).
Thats all I can say. Maybe gurus can have a look at the OctreeSceneNode code...
Good day all.
For me, it was obviously the fault (but according to what criteria ?) of the OctreeSceneNode, because it works fine if I do not use it for the level (but I got this issue only with the level, not the objects).
Thats all I can say. Maybe gurus can have a look at the OctreeSceneNode code...
Good day all.
--
Lideln, France
Lideln, France
Yeah i've had problems with the targets i'm shooting at losing triangles as well, but that only occurs when i'm using the FPS camera to do some debugging, luckily i don't need to use the FPS cam at all in this project so that's not a problem right now!bitplane wrote:bah. okay i think we can safely call this nvidia's fault. i can't recreate it in 1.1, with vsync turned on, or with a 16 bit desktop.
it changes depending on how many meshes are being rendered, what's in front of them, their transformation but not in a predictable way.