Hi we are working on a project and during runtime when we press the “apostrophe” key or type in “enableGDT” in the console, the gameplay debugger does not show up. We did not change our bindings and this feature works on all other projects but this one. Anyone have a solution as to why this feature is not working? I have been searching online for answers but cannot seem to find one. Anyone have an answer?
Hello Maelstorm Games,
We currently have a bug report in our system that has yet to be fixed that states that using US International Keyboard Settings causes the Gameplay Debugger to not show up when using the apostrophe key. Can you check to see if these are the settings that your keyboard is using and change them to see if that is the cause?
Edit: I missed the part about it working correctly in other projects, meaning this is likely not the cause. I’ll look into other possibilities.
I’m curious, was this feature something that worked previously for this project or has the gameplay debugger been broken for this project since the first time you tried? Also, would it be possible to share the project that this is occurring in? Since I haven’t been able the reproduce the issue, I’ve been unable to do any debugging or anything of the sort. If it needs to remain private, you can send a link to me through a private message on our forums. [Here is a link to my profile.][1]
Hi , thanks for your response. We have the keyboard settings right because we can open up other projects and use the UE4 internal gameplay debugger. It just fails to recognize to work with our current project. Let me see if I can send you a build. This feature used to work but I believe it messed up when our previous programmer tried to convert the file from 4.8 to 4.9 and debugging using C++.
Do you happen to have any of those previous versions where the debugger did work? If so, could you try making a copy of one of those, converting it to 4.10 and then testing to see if just converting it caused it to break? Any additional information would be helpful. If this is a bug, the first step is getting a reproduction case so that the cause can be looked into.
We haven’t heard from you in a while, Maelstorm Games. Have you had a chance to work on this issue or uploading a build that reproduces the issue? In the meantime, I’ll be marking this as resolved for tracking purposes.
Thank you for sending me the project. I’ve taken a look and it seems like the Gameplay Debugger is only having issues on what seems to be your primary map, (The one located inside of the Maps folder. I would rather not say the name for privacy reasons). Every other map doesn’t seem to have the issue. It could be related to the influx of log messages and Print Strings. Could you take a look at removing some functionality (in a copy of the project perhaps) to see what may be causing it to be ignored?
I have the same issue, can’t open the debugger via console command “enableGDT”. What is the current command to open the debugger?
I’m not exactly sure what the command is so I’m going to ask about that, but in the meantime, you should be able to change the “Activation Key” binding in Project Settings > Gameplay Debugger and use that to open the debugger.
That worked, thanks!
I’m actually still having this problem, and neither EnableGDT or Activation Key rebinding will work for me! I’m using Unreal Engine 4.22 on a fairly sparse level without many other print statements. My keyboard isn’t set to International layout.