[Latest 4.3 beta causes crawler to rotate at wrong direction]

1)Create new project with latest beta 4.3.

2)Open the AI and event map.

3)Play the game and let the crawler attack you.

 

You will noticed that the crawler will rotated or flipped at wrong direction while attacking you(not while walking)

 

https://www.dropbox.com/s/6zbckjic4cj3lvj/20170126072306_1.jpg?dl=0

[C++ vs Lua]

Thank you guys.

[C++ vs Lua]

Is there a speed difference between those two ? How much speed difference would you expect ?

[Frame limiting or frame smoothing]

Wohoo. I'm impressed with leadwerks community. I wonder why I left Leadwerks last year..

 

Thank Brutile. It works, sorta. I think I get it now. Need few tweaks.

 

Thanks again.

[Posteffect collection]

Thank You!

[Posteffect collection]

Anybody still have a copy of the shaders ? Can you please share it again ? I

 

Thanks

[Please add Camera movement and pan speed on toolbar or viewport]

@gamecreator thanks for the suggestions. But still it would be nice to have the control on main screen and not having to go into Tools->Options->Viewports everytime I want to slow down or speed up the camera.

 

Sometimes I want to move around the map to see If I missed something. Speed up or slow down button or options on the main screen would really help. There is still a lot of space on the toolbar.

[How to Increase viewport range ?]

I'm currently testing a large terrain (4kx4k), but in viewport it is hard to see the terrain since it is clipping everywhere. I can see the water but not the terrain. So It is kinda weird.

 

https://dl.dropboxusercontent.com/u/65841566/Terrain%20view%20distance.jpg

 

I already set the terrainquality to 2.

world:SetTerrainQuality(2)

 

Is there a way to change the max view distance of the terrain on viewport ?

[Please add Camera movement and pan speed on toolbar or viewport]

That is not enough for 4kx4k Terrain.

[Please add Camera movement and pan speed on toolbar or viewport]

Like the topic title said. Please make them available on the main screen

It really hard to speed up or down the camera if you have a large terrain or level.

[Frame limiting or frame smoothing]

@Josh

 

Example ? If I want to limit it to 30fps or 60fps ?

[A Demon's Game - Issues found thus far.]

@lxFirebal69xl

 

For the number two bug, the screen stretches too much or something. I think I have the some problem when playing your demo few weeks ago. Forgot to report it to you and Josh. Sorry.

 

It could be because of nvidia DSR. Somehow it does not play nice with Leadwerks or your game. If the user installed NVIDIA Geforce Experience, it will sometimes enabled DSR automatically. So the user does not even know that it is even enabled. Also I'm using dual monitor setup (extended). Might be the cause of the problem also ?

 

To fix this issue currently is disable DSR from NVIDIA control panel. Hopefully Josh can replicate and fix this officially without user need to disable DSR from NVIDIA Control Panel. (If it is Leadwerks problem and not your script or something)

 

**I just tested this again to confirm. Yes It is fixed with DSR disabled.

[Leadwerks 4.2 RC4 Flashlight causes alot of performance hit]

@genebris

 

I understand, but not every user like to play their game with vsync off.

[Frame limiting or frame smoothing]

Yeah. Do a little digging and found out about Time:Step() . If i added this before Time:Update() , the stuttering is mostly gone. It is now smooth when rotating around object with vsync on..

 

But adding a Frame lock or frame limit manually like 30 , 60 or something might be better. For example I want to lock it to 30 or 45, I dont think this is possible for now unless using third party tool.

[Leadwerks 4.2 RC4 Flashlight causes alot of performance hit]

Adding Time:Step() before Time:Update() in the Main.lua will solve this micro stuttering and jerky issues for my case.

 

http://www.leadwerks.com/werkspace/page/api-reference/_/time/timestep-r501

 

Well you learn something new everyday..

 

So I guess when published our game, we can let the user to have the option to turn off frame cap or not this way ?

 

Or there is more elegant way to do this ?

[Leadwerks 4.2 RC4 Flashlight causes alot of performance hit]

..

[Frame limiting or frame smoothing]

I would like to request frame limiting or frame smoothing built into the engine. Currently I and others encounter these strange bug , stuttering or jerkiness when rotating or when looking at certain angle with flash light

 

http://www.leadwerks.com/werkspace/topic/9182-frame-drops-when-rotating-camera/page__st__20

 

and this

 

http://www.leadwerks.com/werkspace/topic/15387-leadwerks-42-rc4-flashlight-causes-alot-of-performance-hit/

 

 

Frame limiting based on user monitor refresh rate or even let user define their own preference would be a cool features to make leadwerks game smooth and not jerky or stutter.

 

My current solution is to install MSI afterburner and set the frame limit manually to 60 (based on my monitor refresh rate) would be great if this is built into the engine especially when vsync is on.

[Leadwerks 4.2 RC4 Flashlight causes alot of performance hit]

@reaper2259 it is as default as what is in the example. So I assume Josh already make the optimization.

 

@Josh

 

Found the problem and a short term fix. Install MSI Afterburner and in the Rivaturner Statistic Server, Set the frame limit to 60 (To my Monitor refresh rate). Solved my problem with the flashlight and rotating around object microstuttering.

 

Actually my fps when rotating is 60fps but somehow it is not smooth and jerky. Limiting the frame to 60 in Msi afterburner solved this. The jerky or stuttering happens even when Vsync is on in the Main.lua.

 

I think I know why my friends that is using higher performance card (980ti) said that leadwerks game is not smooth also.

I hope Josh can come out with some sort of targeting frame rate settings or frame rate smoothing or something.

 

I suspect user with higher GPU speed may see this stuttering effect more.

 

I would like to request some sort of frame smoothing or frame limiting features built into the engine if possible.

[Frame drops when rotating camera]

Found the problem and a short term fix. Install MSI Afterburner and in the Rivaturner Statistic Server, Set the frame limit to 60 (To my Monitor refresh rate). Solved my problem with the flashlight and rotating around object microstuttering.

 

Actually my fps when rotating is 60fps but somehow it is not smooth and jerky. Limiting the frame to 60 in Msi afterburner solved this. The jerky or stuttering happens even when Vsync is on in the Main.lua.

 

I think I know why my friends that is using higher performance card (980ti) said that leadwerks game is not smooth also.

I hope Josh can come out with some sort of targeting frame rate settings or frame rate smoothing or something.

 

I suspect user with higher GPU speed may see this stuttering effect more.

[Frame drops when rotating camera]

The problem do exist since i bought leadwerks last year.

[Frame drops when rotating camera]

Not sure if I should bring back old topic. But is the mouse rotating around object stuttering is a known bug or fixed ? I get a strange stuttering when I try to rotate while looking at the stairs railing in the AI-Event demo.

 

Windows 10 64Bit

GTX970

 

My settings

1920x1080, msaa2, vsync=on,anisotropy filtering=16, fullscreen on.

 

Funny thing is, I want to record and show this to Josh, when I turn on Shadowplay and try to record it, the stuttering when rotating is almost gone. But if I turn off recording, the stuttering is back.

[Leadwerks 4.2 RC4 Flashlight causes alot of performance hit]

Flashlight will dropped performance from 60 to 43-48ish when it is on, is normal ? The framedrop is steady, it is not just dropped at certain time and coming back up. It will stays at the fps until I move the mouse or look at other angle.

[Leadwerks 4.2 RC4 shadow bug on rocks as vegetation]

@macklebee , thank you!. All the rock material are missing Shadow shaders.

 

 

@Josh

 

This is still considered a bug on the DLC but not on the engine. I hope this is fix so that we dont need to do this every time importing this DLC into our projects.

 

Thanks

[Leadwerks 4.2 RC4 Flashlight causes alot of performance hit]

1)Create new project (FPS Template)

2)Open "07-AI and Events.map"

3)Disable Vsync ( Main.lua line 81 context:Sync(false))

4)Play the game, you will noticed that when the flashlight hit "controller.mdl" at certain angle the performance drop is quite big.

 

 

These screenshots are at default settings and resolution (except vsync is off)

 

1)Flashlight on

https://dl.dropboxusercontent.com/u/65841566/Leadwerks/Leadwerks%204.2RC4%20Flash%20part%201.jpg

 

2)Flashlight off

https://dl.dropboxusercontent.com/u/65841566/Leadwerks/Leadwerks%204.2RC4%20Flash%20part%202.jpg

 

 

1)Flashlight on

https://dl.dropboxusercontent.com/u/65841566/Leadwerks/Leadwerks%204.2RC4%20Flash%20part%203.jpg

 

 

2)Flashlight off

https://dl.dropboxusercontent.com/u/65841566/Leadwerks/Leadwerks%204.2RC4%20Flash%20part%204.jpg

 

 

 

If I change the resolution to 1920x1080, msaa=2, fullscreen , anisotropy filtering=16, vsync on and lighting to "2", it will easily drops to 45-48 ish at the same angle or room. If I turn off the flashlight, the speed will be 60fps.

 

My spec

I72600k

8GB

970GTX Latest driver

Windows 10 64bit

 

 

These screenshots are from (1920x1080, msaa=2, fullscreen , anisotropy filtering=16, vsync on and lighting to "2")

 

1)Flashlight on

https://dl.dropboxusercontent.com/u/65841566/Leadwerks/Leadwerks%204.2RC4%20Flash%20part%206.jpg

 

2)Flashlight off

https://dl.dropboxusercontent.com/u/65841566/Leadwerks/Leadwerks%204.2RC4%20Flash%20part%205.jpg

 

 

 

This bug or performance impact causes some stuttering to happens. The performance drops will remain there until I turn off the flashlight.

[Leadwerks 4.2 RC4 Leadwerks still retains previous deleted layer]

Windows 10 64Bit

 

1)Create new project (FPS template)

2)Open "08 Terrain.map"

3)Add Nature model pack dlc

4)On Terrain->Vegetation->Add "formation5.mdl" as the layer

5)Turn on shadows for the formation5

6)Paint on terrain

7)Delete the "formation5" layer after painting

8)Add new layer for example using "pine01.mdl"

 

You will noticed that the previous painting on the terrain(which is already deleted) is retained and it is now switched from "formation5.mdl" to "pine01"

 

Not sure if this is really a bug. But I was thinking that all information related to deleted layer should be cleared and deleted ?