metaphorset

tindolt, you might take a look at the pinned topic "graphical glitch" at the top of the page. This goes on since last year and yet no solution available.

@Josh. I just did a quick test with the basic FPS Controller and can confirm that ThePhoenix' solution works. Unfortunately I haven't much time right now to create something bigger with water in it.

Ok, so I spent nearly a month with Unreal Engine now, because I can't use LE at all due to this bug. Still no solution? @Josh, do we have a chance to track the problem down somehow?

Using LE 4 Preview now. Latest AMD Driver 15.12 is out and installed, still no improvement.

@slimwaffle, that's exactly what I meant when talking about the perspective mode and turning on antialias. It doesn't matter which antialias I use, though. I already played with the antialias settings in the new radeon settings tool. I changed them for LE and also for my test applications but the graphics are still buggy.

Hi, so there's still no update on this, I guess?

Hi Guys, not sure if my last posting got lost, so I'll try again... I have the same problem with the newest AMD driver and the previous one as well. I'm not sure when it started since I haven't been into Leadwerks a few months. Here's what I found out: Starting LE with one of the demo templates everything seems ok in the editor, as long as I do not change the perspective view to single viewport. It shows the same kind of rendering as in the image you see in the first post. This is the case when the antialias option in graphics options tab is set to 'none'. Everything above works fine.

Guys, I also suffer from this problem. Don't know when it started, since I haven't used LE for quite a while now, but I switched to the newest driver (15.11) and it's still there. What I found out: When i start Leadwerks up and create a new project everything looks fine in the editor. But as soon as I switch the perspecitve mode into single viewport it looks exactly like the screenshot in the first post. I fiddled with LE's graphics settings and found out that Antialias was set to 'none'. As soon as I changed that everything was looking fine. But well, the problem is still there when I hit 'run' or 'debug'.

Bro, I feel you. Been there, done that - at least I tried (not with leadwerks, though). Rick has a point. You might want to take a look at the pros in the gaming industry and then try to understand why they do what they do. If you want to make an open world game like... say <famous-dragon-slayer-game-with-talking-cats> you need to consider a lot of things here since the player might have access to the quest at any time during gameplay. There's a whole lot of scripting involved to make even tiny quests feel "real". Then there's a lot of testing ahead, since not only the player's actions within the quest line can break the quests, it's also other quests or game mechanics that can do so. You should start small, get a feeling for what's possible with the engine and then move on to bigger things. If you have this one big vision of how your game should work it's quite frustrating when you discover that the engine itself can't handle it. In the End there's no big difference between "bring me this I'll give you that" to "go to lots of different places, talk to lots of different NPCs, solve lots of different puzzles, then bring me this and I'll give you that" if the story does not hold up to the effort or your scripting gives away too much hints - or the opposite.