So is it possible that we will ever see some of this newer radar code applied back to some of the FC3 modules ?
Is it modular enough to be done ?
In particular some of the newer IFF/NCTR/TWS code we see in Hornet/Viper applied to F-15, and then furthermore a better API for other 3rd party companies to make their radar code more realistic ?
night and day brother
you will be amazed, trust me, I have tried CV1 and Samsung Odyssey (OG and O+) as well as Rift S. Reverb was by far the better, clearer unit. Especially compared to CV1 and OG
It's very unreadable - 3 things I believe would help resolve
1. the font spacing is nearly non-existent so the numbers run together - very hard to read
2. the font size is really small
3. the MFD's are very 'dim' - so maybe when we can brighten it - will help or set default to be brighter
#1 and #2 are killer right now as I literally have to zoom in just to read the numbers
maybe they had to add this due to the terrible font and font spacing in the F-16 release.... couple that with the dim display, I find it hard to read without zooming in :( . (And I'm in a Reverb!!!)
First off, I use VR, and it's a Reverb, so normally everything is rather easy to read, ie. no issues with the Hornet MFD's.
However, the F-16 has two major issues:
1. The font spacing - ie. radar lock - there is no font spacing. This makes it extremely difficult to read - as well as the font size is very very small. I have to zoom in just to see these basic radar numbers.
2. The MFD's are very dim, so on top of the terrible font size and spacing, the dimmest adds to the difficulty reading the MFDS.
I beg of ED to please address this. One of the items I was most looking forward to was the better contrast compared to hornet, but with this being so tiny and unreadable it's worse.
I literally woke up with a headache after using it last night for a few hours.
Initial setup requires some steps after that you are good to go - this link should help
https://vr4dcs.com/2019/08/19/preflighting-wmr-steamvr-for-dcs/