Jump to content

Leadwerks debugging causes slow FPS


martyj
 Share

Recommended Posts

When debugging leadwerks in visual studios I see a major framerate drop of 1/3rd to sometimes 1/10th compared to that of a released build.

 

I was wondering is there a way I can speed up debugging in visual studio without throwing more hardware at it?

 

I believe the bottlekneck is graphics related as when I run the game on my work computer it performs even slower than my home machine.

 

My work computer has a 650 TI, my home computer has an AMD Radeon 280x.

 

Has anyone else experienced this?

 

I should mention this only happens with a debugger attached to the process.

Link to comment
Share on other sites

Are you using Visual Studio? I found a workaround but it might not always be 100% accurate:

  1. Open up Visual Studio
  2. Select 'Release' instead of 'Debug'
  3. Click Project -> [ProjectName] Properties (a new window should pop up)
  4. Open up "Configuration Properties"
  5. Open up "Linker"
  6. Click on "Debugging" inside Linker
  7. Change "Generate Debug Info" to "Yes (/DEBUG)"

What this does it that the program will remember the flow of the application so when it crashes/reaches a breakpoint, you can still see where it came from. Although, because this is on Release mode, anyone who has your .exe can read your source code. So remember to disable the generation of debug info when you release your game or give it to your friends.

Using Leadwerks Professional Edition (Beta), mainly using C++.

Windows 10 / Linux Mint, Visual Studio 2017. GPU: NVidia GeForce GTX970, CPU: Intel i7 7700K @ 4.20 GHz

Previously known as Evayr.

Link to comment
Share on other sites

I don't want to release my game. I want a way to debug it faster.

 

Without having a major FPS drop.

 

This is debugging without the major FPS drop, just sometimes not as accurate.

Using Leadwerks Professional Edition (Beta), mainly using C++.

Windows 10 / Linux Mint, Visual Studio 2017. GPU: NVidia GeForce GTX970, CPU: Intel i7 7700K @ 4.20 GHz

Previously known as Evayr.

Link to comment
Share on other sites

I use visual c+= in Release mode. I have never tried debugging options. I just use build or rebuild. It tells me the syntax errors. Any runtime errors that come up are due to the last bit of code I wrote and got wrong.

amd quad core 4 ghz / geforce 660 ti 2gb / win 10

Blender,gimp,silo2,ac3d,,audacity,Hexagon / using c++

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...