hyperionlord

did you find any tips or hints in this regard? I also found Three.js to run slowly in fullscreen.. also, did you find a way to prevent the tearing that occurs?

that is wierd! Three.js documentation isn't always up to date, it seems like new versions are released frequently so it's not surprising. I found the best way to track down three.js issues is to get the non-minified library which is still in one big file (which is about 800k instead of 479k) and use that instead. makes debugging a lot easier.

did you fix this yet? I've spent the last week trying to solve black texture problems, so I have some idea about them. Try double checking the file-names are correct and uploaded in the right places.

never mind, I figured it out this weekend (sort of).. I just re-wrote the EffectComposer so it does not have a read and write buffer, just a writebuffer, and got rid of the needsSwap thing as well. This will certainly be more than adequate for what I wish to do with it anyway!

If I had to say, I'd guess it was the draw order was being altered? are you sure the water is being rendered last in order, regardless of where the player character is.. you could for example try setting the sort order yourself, or putting them in a different scene.

Hello, there, I am currently developing a little Three.js web-game (just for fun), its a 3d sort of game where you will eventually have to run around and shoot stuff. I`m working on the "world" bit of the game at the moment, which is some sort of blocky world. I've been working on this by myself for the past month or so, but run into a little problem that I simply don't have a clue how to fix, and was hoping someone else had run into the issue before, or could diagnose the fix. its a problem in the rendering of the scenes, basically I have two Three.js scenes, one for the background (stars, sun, sky etc) and one for block world in the game, they are rendered one after another using a slightly hacked version of the EffectComposer to layer one rendered scene on top the other. The issue i`m having is that for whatever unknown reason the cloud / sky layer scene appears to be rendering "one frame behind", i.e. if you move the mouse quickly, you can see that it takes the background one frame to catch up with the foreground. i've investigated all sorts of potential causes, such as the camera not being updated in time, or half way between the scenes, but so far, I've not found a solution. If someone else has ran into the problem and knows the answer, or just wants to be adventurous and look at my source code (put your special javascript noob filter glasses on first though) that would be awesome. The 'game' is currently located at hyperioncube.com/test only works in chrome and firefox for the moment, and for some reason there is another bug with the pointer lock that means that sometimes pointer lock fails, and you cannot move. I've seen the exact same issue in other games as well, such as helloRun, so that one is less annoying than the sky thing. Oh yeah, i'm constantly working on it, usually during the evenings, so if you go to the page and its all completely broken, don't be surprised!