So I found this really annoying bug that works for AIR. If people have “W” key set as pitch nose up/down and the “S” key as pitch up/down, then when you type in chat something that ends in the letter W or S, then your plane just dives and you can’t really pull up. The only way to do so is to type the opposite key (if you typed in W and are diving uncontrollably, then type S in chat) to reverse the bug. Can someone report this for me/or teach me how?
Uhh…and how do I record a video/and take a screenhot? (my print screen key not working in WT and whatever key I set up as screenshot in settings in WT doesn’t work).
You can use any program which allows recording like OBS Studio, Medal TV, NVidia Shadow Play, what ever you can have to record.
2 Likes
I have no clue what that mysterious new technology is.
Yes, that happened to me. Thought it was my keyboard that got stuck. Another solution is to enter the chat again (without having to type or send anything, and getting out again.
Probably have to send a clog file too, as a video doesn’t confirm what you’re pressing, only what you see.
If you have windows, you should be able to record a video by pressing Windows key + shift + S.
In Mac it should be Command key + shift + 5 if I’m not wrong. Google might help out too. To start and stop the recording you might have to press alt so the cursor works to press the start/stop button.
1 Like
If you have Windows 11 OS you can press Windows + G it will open a XBox overlay which allows you to record the screen and save it to your computer. If I’m not wrong it’s also available in Windows 10. If you have no options use your smartphone and try to record a clear footage of the issue.
1 Like
Thanks! Now I can record. (and do screenshot contests!) You are a true savior!
IG that might be better since it shows what keys I press. Thanks!
Don’t actually record a video. It’s not appreciated.
Go into a live match and reproduce the bug. Accept that you will die. Return to hangar and “Save Replay.”
You will now have a replay file under
*\SteamLibrary\steamapps\common\War Thunder\Replays
Also important, close warthunder so that you generate a clog at
*\SteamLibrary\steamapps\common\War Thunder.game_logs
Might also wish to take a screenshot when the bug occurs, which is saved at
*\SteamLibrary\steamapps\common\War Thunder\Screenshots
Finally, win+r and type “dxdiag”, save your results to a .txt file somewhere convenient.
With that done, go to
https://community.gaijin.net/issues/p/warthunder
“New Issue.”
Then write a bug report as follows if you want to be taken seriously:
### Brief description of the issue
lorem ipsum
### What was expected to happen
Lorem ipsum
### What actually happened
lorem ipsum
### Steps to reproduce
HERE WRITE OUT STEPS AS IF YOU WERE EXPLAINING THINGS TO YOUR GRANDMOTHER.
Seriously. Don't make ANY assumptions. Don't hand-wave any steps.
Describe exactly what the relevant keyboard binds are
Describe exactly what button presses you make under what conditions in what aircraft in what mode
Do not leave out anything that you think is "common sense."
Please follow this advice for the sanity of all QA/QC and devs that exist
### Additional notes
Anything you could not fit under anything of the above.
Then upload your dxdiag output, your .clog, your replay and fill in what game version it happens under.
Oh and obviously replace my filler text with what’s sensible.
2 Likes
If it happens in custom battles too you can also do so, this way you lose nothing, and you can try multiple times if it’s not consistent. They also have their own replays if I’m not wrong.
1 Like
I have that happens some times as well, I just mash all of the awsd keys until it stops, usually works first try for me
1 Like