Jump to content

Recommended Posts

Posted

Okay, I haven't tried this yet, but I've read the moaning about NVG's not being able to focus inside the cockpit, or more correctly, being focused for distances outside the cockpit.

 

To use TPD or DMT you need to use the MPCD's and see what is displayed to TDS onto a target, but if you cannot even focus inside the cockpit... :doh:

 

Also, if you cannot turn the MPCD brightness way down for using with NVG, isn't it going to blind you?

 

Without NVG's you still have FLIR, both in INS and TPD, so you can search for targets, but I'm guessing, incoming SAM's might be pretty hard to detect at all, especially when their initial thrust is passed. I'm imagining that a SAM will be easier to detect in NVG at night, since it ought to stand out against a cold background, even after the engine is out.

 

So for night-time missions, NVG or NVGn't?

When you hit the wrong button on take-off

hwl7xqL.gif

System Specs.

Spoiler
System board: MSI X670E ACE Memory: 64GB DDR5-6000 G.Skill Ripjaw System disk: Crucial P5 M.2 2TB
CPU: AMD Ryzen 7 7800X3D PSU: Corsair HX1200 PSU Monitor: ASUS MG279Q, 27"
CPU cooling: Noctua NH-D15S Graphics card: MSI RTX 3090Ti SuprimX VR: Oculus Rift CV1
 
Posted (edited)

Issue is that Eagle Dynamics has not made NVG's adjustable yet. I rather have NVG's set up at HUD height to not interfere with reading gauges and instruments.

 

I still think NVG's are the way to go since the FLIR is also a bit problematic atm. Set up everything you can on ground and have a toggle button ready for NVG's off/on.

Edited by Schmidtfire
Posted

I use the space bar for my nvgs. And I fly in VR so my whole screen is nvg not the to 2/3 like when you aren't in VR (different issue all together).

 

I prefer the nvg offer flir, mainly because it's all around vs HUD view, which is very limited. I just to the space bar to look inside. I tend not to use weapons I need to look in the cockpit for at night, so bombs/rockets/gun and make use of jtacs for lazing or it markers. That's the beauty of this aircraft, the internal LST.

 

If I'm going to use Mavericks or the TGP I won't use nvgs while I'm in attack mode.

 

If you set up the displays for night (turn the EHSD map off, DMT to nite mode, don't use the TGP) I haven't really had an issue at night, even with nvgs on. But I adjust the gain on them so it's not too big of an issue.

 

I see a lot of people complain about the mpcds not adjusting, but honestly the warning lights are a bigger issue for me. Get the low fuel light on with the goggles on and tell me how you like that. Or the master warning or caution. That blinds me, not the displays.

 

Sent from my SM-G960U using Tapatalk

Aurora R7 || i7K 8700K || 2TB 7200RPM SATA 6Gb/s || 2TB M.2 PCIe x4 SSD || GTX 1080 Ti with 11GB GDDR5X || Windows 10 Pro || 32GB Dual Channel DDR4 at 2667MHz || Virpil Warbird Base || Virpil T-50 Stick || Virpil MT-50 Throttle || Thrustmaster TPR Pedals || Oculus Rift

Posted (edited)

Hey, something I actually know way too much about!

 

So, depending on how you want to approach this.

 

1. IRL per every flight manual I've seen for fixed or rotary wing, ANVIS (NVG's) are basically supposed to be set to infinty focus in flight at all times. The logic there is they don't want pilots screwing around with them and then not having the correct focus/depth perception out of the pit. Even when set perfectly NVG's already give you way reduced visual acuity IIRC 20/40 vision equivalent and in a 40 degree FOV or something like that.

 

2. Depending on the era of aircraft, cockpit lighting was supposed to be NVG "compatible" basically the lights used were at certain frequency, and this was then specifically filtered out by the NVGs for the most part, so you really shouldn't be seeing a ton of overbright light in the pit (This may badly modeled in DCS in general) In my estimation the cockpit lighting might be a bit overdone in NVG mode in most planes I've seen.

 

3. If IRL pilots needed to read an instrument, its actually very easy to glance under/around the ANVIS. which is sort of ok modeled on the flat screen NVG rendition IMO, but as you mention in VR the whole screen is green which isn't great. But there is "frenchy's NVG mod" which may help I haven't tried it yet but its on the list. The other thing is to just flip up the NVG's if you need to be head down in the pit and then flip them back down when needing to look outside.

 

4. MCPD's. This is a point I'm not 100% clear on, at some point in the recent past they did start making the MCPD's NVG readable in some aircraft both in terms of light levels and focus, not sure if that actually applies to the Harrier we have on the focus thing but at a guess the brightness is something they did do.

 

5. SAMS, these should be very visible in NVG's and FLIR when launched (motor is hot and bright) you should see a bright moving dot on launch. Once it burns out, its gonna be real hard/impossible to see SAM's with NVG's, however on thermal they should IRL stand out against the "sky" because sky is ultra cold always, not sure how well any of this is actually modeled in DCS, given they model water as "warm" which it almost never is IRL.

 

6. Practical DCS flying. I map the NVG's to a HOTAS button and on/off them at will depending on what I need to be doing. I do use the nite mode for DMT, and turn the map off on the EHSD (in general actually, unless navigating). I'm gonna look into Frenchy's NVG mod too.

Edited by Harlikwin

New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1)

Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).

Posted
Issue is that Eagle Dynamics has not made NVG's adjustable yet.

 

Given that they are supposed to be used to look outside at infintiy focus per every document on the topic I've seen they probably shouldn't.

New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1)

Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).

Posted
Given that they are supposed to be used to look outside at infintiy focus per every document on the topic I've seen they probably shouldn't.

 

Given all the other limitation around using NVGs in a SIM vs real life, I'd personally rather just be able to see inside my cockpit without having to hit my spacebar. But that's just my opinion.

 

But there is only so many times I can lift my VR goggles off of my head because I forget they aren't actually NVGs before I get frustrated.

 

But to each there own

Aurora R7 || i7K 8700K || 2TB 7200RPM SATA 6Gb/s || 2TB M.2 PCIe x4 SSD || GTX 1080 Ti with 11GB GDDR5X || Windows 10 Pro || 32GB Dual Channel DDR4 at 2667MHz || Virpil Warbird Base || Virpil T-50 Stick || Virpil MT-50 Throttle || Thrustmaster TPR Pedals || Oculus Rift

Posted

Well, thats the whole sim vs IRL debate.

 

Well I just think they should implement the NVG's better in VR. A rift has ~100 deg FOV, and its way wider than an AVIS FOV is (40) so they could easily do that, or maybe make it bigger. Sadly using NVG's IRL is like looking through a toilet paper tube, you have to keep your head on a constant swivel.

 

I haven't tried it but this may help.

https://forums.eagle.ru/showthread.php?t=151646

New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1)

Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).

Posted
Well, thats the whole sim vs IRL debate.

 

You are correct there, haha

 

Well I just think they should implement the NVG's better in VR.

 

I 100% agree with you

 

 

I'll try it out and report back. Thanks, something like that is exactly what I was hoping for!

Aurora R7 || i7K 8700K || 2TB 7200RPM SATA 6Gb/s || 2TB M.2 PCIe x4 SSD || GTX 1080 Ti with 11GB GDDR5X || Windows 10 Pro || 32GB Dual Channel DDR4 at 2667MHz || Virpil Warbird Base || Virpil T-50 Stick || Virpil MT-50 Throttle || Thrustmaster TPR Pedals || Oculus Rift

Posted

This is one of those difficult areas to simulate. But I think either adjust the NVG’s so they are default set a little bit higher on the screen. Or make it dynamic. When you look down, you sligthly push the NVG fov up in Y axis on screen. Sort of simulating a glance under.

 

Use the same tech as with the JHCMS on the F/A-18C, but adapt it to make the NVG’s animated dynamicly.

Posted

Wow, thanks for all the responses :)

 

I was going to try out Frenchy's NVG mod :D and then I read that it won't pass MP integrity check :cry:

 

I'm trying to work my way up to MPing on Georgia At War, so Frenchy's NVG mod won't help me there.

 

I guess I'll just have to see what I can work out.

When you hit the wrong button on take-off

hwl7xqL.gif

System Specs.

Spoiler
System board: MSI X670E ACE Memory: 64GB DDR5-6000 G.Skill Ripjaw System disk: Crucial P5 M.2 2TB
CPU: AMD Ryzen 7 7800X3D PSU: Corsair HX1200 PSU Monitor: ASUS MG279Q, 27"
CPU cooling: Noctua NH-D15S Graphics card: MSI RTX 3090Ti SuprimX VR: Oculus Rift CV1
 
  • Recently Browsing   0 members

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