Jump to content

the render is sick


Recommended Posts

4 hours ago, Flappie said:

@edison_trentEmpty these folders and tell us if the issue remains:

  • C:\Users\username\Saved Gmaes\DCS...\metashaders2\
  • C:\Users\username\Saved Gmaes\DCS...\fxo\

 

That's as good an idea as any--since 2.7 is a major update, it's a good plan to wipe out fxo and metashaders2 and let DCS rebuild them from scratch.

 

Also, SLI has never gotten along well with DCS. I just don't think DCS is coded to make use of it. If all else fails, disable one graphics card and try again.

Also, check for excessive overclocking of GPU and VRAM, which can cause this too.

 

OP, keep us posted, I'm curious how it works out for you.

 

AD

Kit:

B550 Aorus Elite AX V2, Ryzen 7 5800X w/ Thermalright Phantom Spirit 120 SE, 2 x 16GB Kingston Fury DDR4 @3600MHz C16, Gigabyte RTX 3070 Windforce 8GB, EVGA SuperNova 750 G2 PSU, HP Omen 32" 2560x1440, Thrustmaster Cougar HOTAS fitted with Leo Bodnar's BU0836A controller.

--Flying is the art of throwing yourself at the ground, and having all the rules and regulations get in the way!

If man was meant to fly, he would have been born with a lot more money!

Link to comment
Share on other sites

9 часов назад, Flappie сказал:

@edison_trentEmpty these folders and tell us if the issue remains:

  • C:\Users\username\Saved Gmaes\DCS...\metashaders2\
  • C:\Users\username\Saved Gmaes\DCS...\fxo\

i did it.

5 часов назад, Aluminum Donkey сказал:

 

That's as good an idea as any--since 2.7 is a major update, it's a good plan to wipe out fxo and metashaders2 and let DCS rebuild them from scratch.

 

Also, SLI has never gotten along well with DCS. I just don't think DCS is coded to make use of it. If all else fails, disable one graphics card and try again.

Also, check for excessive overclocking of GPU and VRAM, which can cause this too.

 

OP, keep us posted, I'm curious how it works out for you.

 

AD

i did it and it did not help. if i disable one card it's working well (clouds are amazing, thanks ED). such a problem was with the radar flickering in AG mode (2.5.6). ED has resolved this problem. I was happy not for long...

Link to comment
Share on other sites

10 hours ago, Flappie said:

@edison_trentEmpty these folders and tell us if the issue remains:

  • C:\Users\username\Saved Gmaes\DCS...\metashaders2\
  • C:\Users\username\Saved Gmaes\DCS...\fxo\

 

I've checked these folders after the update.

The metashaders2 was empty (and still is, even after running 2.7 a couple of times).

The fxo folder only contains files from "after" the update.

 

Which means that were flushed during the update process. So no need to delete/empty them anymore.

Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind combat pedals, TrackIR4, Rift-S.

Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!

Link to comment
Share on other sites

36 minutes ago, Lange_666 said:

I've checked these folders after the update.

The metashaders2 was empty (and still is, even after running 2.7 a couple of times).

The fxo folder only contains files from "after" the update.

I asked him to try it out because someone else fixed a strange visual bug where an Mi-8 cockpit was all magenta using this method.


Edited by Flappie

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

1 hour ago, Lange_666 said:

Which means that were flushed during the update process. So no need to delete/empty them anymore.

After update(and repair) and before starting 2.7 for the first time i had still the old files and manually deleted them before starting 2.7 for the first time.


Edited by unknown

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Thanks. This is what I can see:

 

Your Windows is dated (November 2019). You should consider an update.

=== Log opened UTC 2021-04-17 05:33:18
2021-04-17 05:33:18.100 INFO    DCS: Command line: "C:\DCS World OpenBeta\bin/DCS.exe"
2021-04-17 05:33:18.100 INFO    DCS: DCS/2.7.0.4625 (x86_64; Windows NT 10.0.18363)

 

Your SLI is well detected by the game:

2021-04-17 05:33:42.601 INFO    DX11BACKEND: NVIDIA API init OK
2021-04-17 05:33:42.604 INFO    DX11BACKEND: NVIDIA Display Driver Version 46611.r466_04
2021-04-17 05:33:42.604 INFO    DX11BACKEND: SLI MODE Enabled on 2 Cores.
2021-04-17 05:33:42.604 INFO    DX11BACKEND: GPU count:2

 

If you don't want to try a Windows update, maybe try to disable these ingame options:

  • V-sync
  • Lens Effects
  • Depth of Field
  • Fullscreen

 

 

 

 

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

  • 4 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...