Fine by me, not like I am trying to give you a hand while doing my own things either.
Checked up with a 1080ti user in my discord and no issues reported either, but then again their system does not match yours neither does their user config.
Personally I am on a 3070, no issues and the 1060 in my old system also gives no issues.
I have a fresh windows installation, freshly downloaded and installed everything.
How would my system be faulty?
Motherboard in UEFI mode, VGA has the nvidia uefi bios update.
DDU to remove drivers entirely as well before re-installing?
Compatibility mode?
Cause the game works flawlessly for me and I’m running your CPU.
Just an RTX 4070 instead cause I play at 4k.
32GB of system RAM cause I like having a browser open while playing games.
SSDs only for storage.
I have no 1080 Ti friends to ask cause they’ve all upgraded at this point.
When the game is working for others, it’s either an edge case with the software or it’s the computer running the software… usually both if it’s an edge case.
I remember when my RTX 2070’s known hardware defect finally showed itself, but would only show itself on War Thunder and one other title, and would run flawlessly for other games.
1 Like
I tried enabling CSM in bios, did not matter.
I reinstalled drivers multiple times with DDU.
Anyway possible to launch an older version of WT?
Does the dxdiag made by the WT launcher show you the correct amount of VRAM?
dxdiag is a Microsoft Windows command, not War Thunder.
It does show you the correct VRAM.
It does not tell you if your GPU’s VRAM is still good or if a module has partially failed, or whatever else.
I don’t know how to test GPU VRAM personally.
If you have a backup GPU I would try that.
If not… IDK.
You should test it… I just had the same on mine…
---------------
Display Devices
---------------
Card name: NVIDIA GeForce RTX 3060
Manufacturer: NVIDIA
Chip type: NVIDIA GeForce RTX 3060
DAC type: Integrated RAMDAC
Device Type: Full Device (POST)
Device Key: Enum\PCI\VEN_10DE&DEV_2504&SUBSYS_397D1462&REV_A1
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 44846 MB
Dedicated Memory: 12115 MB
Shared Memory: 32731 MB
Current Mode: 5120 x 1440 (32 bit) (120Hz)
---------------
Display Devices
---------------
Card name: NVIDIA GeForce RTX 3060
Manufacturer: NVIDIA
Chip type: NVIDIA GeForce RTX 3060
DAC type: Integrated RAMDAC
Device Type: Full Device (POST)
Device Key: Enum\PCI\VEN_10DE&DEV_2504&SUBSYS_397D1462&REV_A1
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 4095 MB
Dedicated Memory: 3072 MB
Shared Memory: 1023 MB
Current Mode: 5120 x 1440 (32 bit) (120Hz)
Something is wrong with the dxdiag from the launcher.
1 Like
Start the WT launcher, click the tool icon on the top right corner.
Click the button diagnostic files, and wait for the output.
Check the dxdiag.txt.
Read the comments before. I just showed that WT runs dxdiag in 32bit, and it also shows in the launcher log that the vram is only ~3gb.
Thank you so much!!!
Finally a confirmation.
It’s just for that DxDiag though, I’d send through both versions to have both there.
It is a question though if this is actually what’s hitting you in the client overall, and even why it’s happening in this manner if it is.
I’d try running the 64 bit aces.exe and see if that makes anything happen different. I’d also look at task manager and see if the launcher is running the 64 bit version of aces.exe where it should or if it’s doing the 32bit version instead.
(I just checked task manager and mine is running the 64 bit version of aces.exe)
Steam launches the 64bit aces.exe, I checked.
The wt launcher log also has an entry for video memory. It is the same incorrect number that the launcher dxdiag shows.
1 Like
This makes sense since the Launcher was likely never updated to 64bit like the primary client.
I never used auto settings on War Thunder, and I never used the launcher to set settings.
I’ve been using Steam’s War Thunder client since 2016, which stopped using the launcher itself at some point.
32bit is hard limited to 4GB.
The War Thunder client itself is 64 bit.
So the question becomes why is the launcher seemingly trying to force old standards on you.
Never had this issue myself… oh have you deleted the War Thunder files in appdata?
For example:
I have a fresh, crispy, still hot windows install, on a reformatted SSD.
WT redownloaded on a reformatted SSD.
Do you have the same in game issues that I have?
Late loading of ground textures and objects?
After some games most of the ground textures are low quality.
If you change the texture quality in the game, and hit apply, do you get the red message “texture quality reduced…” if you go back in the graphics settings and hover the mouse over the texture quality field?
Yea nah, I got nothing crazy going on.
Windows 11, It’s actually really stable.
I am still on win 10 pro…
Running now a booted memtest on the system RAM, but I am really struggling to see how my system is at fault when everything else works perfectly but WT.
Pretty sad that there is literally no chance to have a proper support from the WT DEVs.
It’s most likely because somewhere along the way it’ll end up being a config/hardware issue usually, and support and tickets are more for account based stuff.
You’ve also got further in this thread with the engagement we’ve had in here.
My launcher log also shows the 3GB of Video RAM, if you’re referring to this line in it:
1.16 [D] videoMemory: 3221225472
I think it’s because the launcher is 32bit (but the game itself is 64bit). This is probably why the 32bit dxdiag also gets started from the launcher.
I have an nvidia 1660Ti with 6GB of RAM. No current issues such as you’re describing with it.
All that we learned here was that the game launches dxdiag 32bit. I already knew from the launcher log that it thinks VRAM is only 3gb.
RAM test shows zero errors.
1 Like