Jump to content

Recommended Posts

Posted

Not sure, if it is a general, or VR problem. But in my TGP and MAV view it's nearly impossible to see any targets. Tried narrow + wide view, different contrast, zoom levels... In TGP you sometimes can see targets, but the MAV view only shows a gray wall and with a bit luck you get a lock on something invisible. Any idea if it is a wrong setting, or a general VR problem?

I9 9900K @ 5Ghz | MSI Z390 Gaming Carbon Pro | KFA2 GTX 1080 Ti | 64 GB Kingston HyperX 2666Mhz | Samsung 960 EVO M.2 NVMe 250GB SSD | Pimax 5K+ | Warthog HOTAS | MFG Crosswind | Wheelstand Pro Flight

Posted

Can you provide a screenshot? Does the problem appear when you use a regular monitor screen instead of VR? Make sure you run the same mission and look at the same target so we can compare.

Posted

Generally speaking, the visibility of targets in the TGP (and Mav view) has decreased significantly with a patch a while ago.

 

As a workaround, you could install one of several terrain mods, most of which fix or at least alleviate the issue, or you could change a value in one of the config files.

 

The ultimate solution, creating a more realistic IR view, is yet to come, but ED have hinted that they're working on it because of the F/A-18C and its TGP, so here's to hoping that the issue will be solved at some point in the future. :thumbup:

Posted

my Constast works now to accurately see the FLIR heat

 

when this is helped with the

 

noisemax = 0.6;

mod

in

\Config\terrain\Extreme.lua

 

(where 'extreme' is the visibility setting in my DCS options)

 

changed to

noisemax = 0.4;

 

this setting change effect ALL landscape render, so 0.5 ok, 0.3 might flatten your landscape render

| VR goggles | Autopilot panel | Headtracker | TM HOTAS | G920 HOTAS | MS FFB 2 | Throttle Quadrants | 8600K | GTX 1080 | 64GB RAM| Win 10 x64 | Voicerecognition | 50" UHD TV monitor | 40" 1080p TV monitor | 2x 24" 1080p side monitors | 24" 1080p touchscreen |

Posted (edited)

Yeah, it's pretty bad on a regular screen, never mind VR.

 

For the TGP, I'm using the TGP Colour Mod and 512 resolution which seems to make up for the bad contrast in 1.5.

 

That said, I'm mostly using IR mode (boat switch forward) to find targets with the TGP.

 

The MAV screen on the MFCD is pretty useless ATM unless you already 'know' where the target is.

 

So my current work flow is

 

DCS A-10C Tutorial:

How to use the AGM-65D Maverick Cued by the Targeting Pod

 

Autopilot Path/Altitude [A]

Counter measures as req'ed [7 to release]

Manual mode

Disp - Dispenser Menu

chaf 002, flar 002, intv 0.75, cycl 05

Save and Return Program

 

DSMS Select Mavericks

Set Mavericks on RH MFCD

Use UFC to set Mav Slew to 1.0 (UFC 1, then OSB8 )

 

Set TGP on LH MFCD as SOI

Boat Switch Forward to Switch IR Modes [R-Ctrl+ RH Arrow]

Find target using Slew controls (Arrow keys)

China Hat Forward-Short to change FOV (R-Shift+Up Arrow)

DMS Up/Dn to Zoom In/Out (R-Shift+POV Hat)

TMS Up-Short to cycle Area/Point track (R-Ctrl+POV Hat Up)

 

TMS Up-Long to set TGP as SPI generator (R-Ctrl+POV Hat Up)

HUD Bottom LH shows TGP as SPI

 

China Hat Forward-Long to slave all sensors to the SPI

(R-Shift+Up Arrow)

 

Maverick as SOI

TMS Up-Short to Lock on SPI

 

-------------------------------------

 

Switch between Gun, CCIP and CCRP using Master Mode button [M]

 

Switch Gun sights using DMS

 

TMS Dn-Long to Reset SPI to Steer Point (R-Ctrl+POV Hat Dn)

 

Optional: Find Targets with TGP

TMS-Right create Mark Point(s) for each target

'Steer PT' Selector to 'Mark'(RH Panel)

TMS Dn-Long to Reset SPI to Steer Point (R-Ctrl+POV Hat Dn)

HUD Bottom LH shows STPT as SPI

Step through Mark Points (A, B, C, etc.) with DMS Up/Dn

Releaseing Weapons when in paramaters i.e. JDAMs CCRP, etc.

 

Note: Mark Zero is last weapon hit/target.

 

Note: I've changed the default keybinds and it's all WIP (these are just flight notes from last night).

Edited by Ramsay
typo's and errors

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted (edited)

Hi Ramsay

Thanks for the tgp color mod link, gonna try that.

Also for sharing your technique, I do the same but didnt know you could cycle mark points with the DMS. (I mapped the autopilot button on the left throttle to the steer point toggle on the UFC)

Now I can have it back, cool.

Edited by dallas48
Posted

That mod does not pass integrity check for me.

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

Posted
That mod does not pass integrity check for me.

 

noisemax =

 

passes integrity

| VR goggles | Autopilot panel | Headtracker | TM HOTAS | G920 HOTAS | MS FFB 2 | Throttle Quadrants | 8600K | GTX 1080 | 64GB RAM| Win 10 x64 | Voicerecognition | 50" UHD TV monitor | 40" 1080p TV monitor | 2x 24" 1080p side monitors | 24" 1080p touchscreen |

Posted

Change the value you mean? And if so, to what?

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

Posted

Haven't tried the noisemax thing myself, but IIRC from another thread a better value would be 0.5 instead of the 0.9 that are set.

EDIT: Regardless of the actual value: Lowering the noise makes the textures more flat. So you can see vehicles better.

 

But on most ground textures just increasing the contrast of the MFCD works decently for me.

Still not great, we will have to wait for the new FLIR implementation by ED, but better than nothing.

  • 2 weeks later...
Posted

Crickets,,,,,,,,,,,,,,,

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

  • 1 month later...
Posted
noisemax =

 

passes integrity

 

"Change the value you mean? And if so, to what?"

 

I never got a response to this, Im sure its a simple thing but initially, I have no idea where and what your referring to? I am still frustrated with this! I have been having guys broadcast their SPI for me and when I slew to it, all I see is the terrain, they cant believe I dont see the target! However, if I zoom into it to the point where (if there was an actual person in there) I could see the guys hair color, I can see the vehicle. Tinkering with Contrast and brightness switches does help a bit, but find once I think I have it set well enough, I switch to say BHOT, and its all screwed up! I have also tried using Mustangs Terrain mod, this did not seem to help. Someone suggested that maybe the graphics settings in the GUI might have an impact, like the draw distance? Any advise would be appreciated. Thanks,

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

Posted
"Change the value you mean? And if so, to what?"

 

c:\DCS\Config\terrain\Extreme.lua

 

'Extreme' or any other that you use in Options 'Visibility Range'

 

find:

 

--Old Noise

land_noise =

{

noisemin = 0.0;

noisemax = 0.4; -- >> default 0.6;

 

(or 0.5)

 

the targets now dont blend in the background

| VR goggles | Autopilot panel | Headtracker | TM HOTAS | G920 HOTAS | MS FFB 2 | Throttle Quadrants | 8600K | GTX 1080 | 64GB RAM| Win 10 x64 | Voicerecognition | 50" UHD TV monitor | 40" 1080p TV monitor | 2x 24" 1080p side monitors | 24" 1080p touchscreen |

Posted

Thanks for the explanation, I believe I understand now,,,,

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

Posted

Other than changing the noise max values, there must be another variable at play here. I changed the value and compared values 4 and 9, with no visual differences? I did confirm the values did take and hold for the Exterme.lua using Notepad++

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

Posted

Fakum, check your "Visib Range" in settings, are you using Extreme setting? If not, editing the extreme.lua won't change anything.

 

You need to change the correct .lua corresponding with your setting. Edit High.lua if you're using high setting, Ultra.lua if your using ultra setting and so on.

Posted

As per the photo above showing my graphics settings, my Vis Range is set to " Extreme" and that is the ONLY .lua I have changed the noise max value in.

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

Posted

ok, I have gone back, disabled ALL MODS, checked to make sure there was not a Config File under User saved games that might be conflicting. Found none, went about changing values again direct in the DCS directory, even went from a value of 0.1 to 1.0 with no difference. What could I possibly be missing that is so simple, yet eluding me?

 

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Config\terrain\Extreme.lua

 

--Old Noise

land_noise =

{

noisemin = 0.0;

noisemax = 1.0;

noise1front = 1000.0;

noise1back = 80000.0;

noise1top = 12000.0;

noise1bottom = 2000.0;

noise1PerSquare = 2.0;

noise2PerSquare = 150.0;

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

Posted (edited)

weird, perhaps you set your monitor manually color changed that inhibits the effect? (dark horse)

 

EDIT:

just checked (couldnt resist)

 

your right, doesnt make a difference ..

 

Perhaps DCS changed the algorithm 1.5.xx somewhere,

what I do know

since, recently (1.5x) I changed my monitor setup(s) & I tweaked my monitors from factory default (NVidia panel),

I do that with an eye on A10C MFCDs so mine is (are) perfect TGP

 

perhaps you can do same to solve your problem

Edited by majapahit

| VR goggles | Autopilot panel | Headtracker | TM HOTAS | G920 HOTAS | MS FFB 2 | Throttle Quadrants | 8600K | GTX 1080 | 64GB RAM| Win 10 x64 | Voicerecognition | 50" UHD TV monitor | 40" 1080p TV monitor | 2x 24" 1080p side monitors | 24" 1080p touchscreen |

Posted

Thank you majapahit, I did not even consider asking anyone to check for themselves as I thought it was me. The good news is that it is not me, the bad news, try and find another solution. I will try what you said with the monitors, but 1st I will take a trip over to the 104th and check the chatter for Mustangs Textures MOD as I know I had seen discussion about noise settings, and at the time, I had no idea what they were talking about. Many thanks,,, wish me luck. thank you also Windsortheater for the suggestion

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

  • Recently Browsing   0 members

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