Jump to content

Recommended Posts

Posted

Hi all,

 

compared to other aircrafts, I am always fiddling and never happy with the FOV in the A10C and the position of the Virtual Head in the cockpit. It's either too forward or too low or who knows what.

Right now I using a FOV of 95 degress in the default view of the snapviews.lua section for the A10C.

I am wondering what you guys are using for FOV and for the V and H degrees in that same section etc.

There's just something wrong with the A10C I think.

 

Am I the only one to feel that?

 

E.

Kaby Lake @ 4.6Ghz - Gigabyte Z170-D3H - 16Gb DDR4 - Gigabyte GTX 1080 G1 OC - Samsung EVO 250Gb SSD - Seagate 1 Tb HDD - HTC Vive - Rift CV1

Posted

I agree with you, I think that the virtual head is too forward; I use TrackIR so I don't notice the height too much. I remember seeing a mod somewhere which changes the position to a supposedly more realistic position but I'm on my phone to won't be able to link it. I would like to find some more info on this matter.

 

Sent from my ONE A2003 using Tapatalk

[sIGPIC][/sIGPIC]

 

 

[TABLE]PC Specs

i7-4790k

GTX 970

MSI Z97 Gaming 5

24 GB RAM

Samsung 850 Evo 240GB SSD

[/TABLE]

 

[TABLE]Equipment

Thrustmaster HOTAS Warthog

CH Pro Pedals

3D Printed TrackIR[/TABLE]

 

Posted
I agree with you, I think that the virtual head is too forward; I use TrackIR so I don't notice the height too much. I remember seeing a mod somewhere which changes the position to a supposedly more realistic position but I'm on my phone to won't be able to link it. I would like to find some more info on this matter.

 

Sent from my ONE A2003 using Tapatalk

I completely agree. I'll look around and see if I can find some info. Also, how are you liking your OnePlus Two? I'll be trying to get from my Two to a Three soon... What about you?

 

[TBS] [TFP] Slydog486, Veteran DCS Noob

 

Sent from OnePlus Two.

PC: MSI Z170A M7, i7-6700K, 32GB Corsair Vengeance LED DDR4-3466, (x2) Asus GTX 1070 8GB STRIX [2-way SLI], (x2) Samsung 850 EVO 500GB, (x2) WD Caviar Blue 1TB 7,200 RPM, EVGA SuperNOVA P2 850W, Windows 10 Home, Phanteks Enthoo Evolv ATX Glass.

 

Periph: Razer - Black Widow Chroma, Kraken 7.1 Chroma, Seiren, Naga Hex; Thrustmaster Warthog, TrackIR 5, Saitek Pro-Flight Rudder Pedals, (x2) 22" 1920x1080, Bose Companion 5.

Posted

It's because of the limitations of older / small screens.

The viewpoint is far enough forward for a user of an old/small screen to see all of, and read, the HUD.

With the current HUD text size/rendering position, if you move your head back, you get a more realistic viewpoint, but can't see all the HUD.

If you then move the HUD render point away (& so decrease the text size) till you can see all of it from a more 'normal' viewing position, the text is so small you can't read it on anything smaller than an HD 30" screen.

Cheers.

Posted

Thanks guys for the feedback.

I should have given you my configuration: I use 3 screens for a total resolution of 5760x1080 and a trackIR as well.

 

So, there's no way to actually change in the lua files any of this?

Kaby Lake @ 4.6Ghz - Gigabyte Z170-D3H - 16Gb DDR4 - Gigabyte GTX 1080 G1 OC - Samsung EVO 250Gb SSD - Seagate 1 Tb HDD - HTC Vive - Rift CV1

Posted
I completely agree. I'll look around and see if I can find some info. Also, how are you liking your OnePlus Two? I'll be trying to get from my Two to a Three soon... What about you?

 

[TBS] [TFP] Slydog486, Veteran DCS Noob

 

Sent from OnePlus Two.

I really like my OP2. I don't think I'll be switching to the OP3 when it comes out as I've only had my OP2 for 3 months...

[sIGPIC][/sIGPIC]

 

 

[TABLE]PC Specs

i7-4790k

GTX 970

MSI Z97 Gaming 5

24 GB RAM

Samsung 850 Evo 240GB SSD

[/TABLE]

 

[TABLE]Equipment

Thrustmaster HOTAS Warthog

CH Pro Pedals

3D Printed TrackIR[/TABLE]

 

Posted

I haven't tried for ages...

I'm sure you could move the default position in previous versions & that I had it set up with a more 'normal' seating position for a while in the Su-27, but you couldn't see all the data on the HUD without leaning forward, and I don't know how (but others may) to make the HUD data fit into the visible part of the HUD with the viewpoint moved back.

Cheers.

Posted

On my machine it seems the text on the A10C HUD is much less crisp than every other module (and for some reason much harder see in bright conditions), even than the KA50 which is an older module.

 

Is there any way, or any mod to make the text sharper?

Posted

Here are my settings in the snapviews.lua file

[13] = {--default view

viewAngle = 95.000000,--FOV

hAngle = 3.292176,

vAngle = -13.841103,

x_trans = 0.251312,

y_trans = -0.055430,

z_trans = 0.010063,

rollAngle = -0.156555

Kaby Lake @ 4.6Ghz - Gigabyte Z170-D3H - 16Gb DDR4 - Gigabyte GTX 1080 G1 OC - Samsung EVO 250Gb SSD - Seagate 1 Tb HDD - HTC Vive - Rift CV1

Posted

One thing to note about the view seeming to be too far away, is that the HUD is designed to be looked at by both eyes. Quite many of the real HUD's take advantage of the fact that the eyes are apart, so in real life your right eye would see the center and left portion of the HUD, and your left eye would see the right half. As the HUD text is optically focused on infinity you soon forget that the HUD glass and the metal frame supporting it even exist.

 

This can't be recreated in 2D obviously.

DCS Finland | SF squadron

Posted

I tried changing the luas before, the problem is that these can get overwritten in missions, MP and SP. so I've kept the default settings.

i9-14900KS | ASUS ROG MAXIMUS Z790 HERO | 64GB DDR5 5600MHz | iCUE H150i Liquid CPU Cooler | ASUS TUF GeForce RTX 4090 OC | Windows 11 Home | 2TB Samsung 980 PRO NVMe | Corsair RM1000x | LG 48GQ900-B 4K OLED Monitor | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5

  • Recently Browsing   0 members

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