Jump to content

Recommended Posts

Posted

I really don't like to have the zoom on the TrackIR z-axis. Never found a setting where it would work as stable and comfortably as an axis on the HOTAS.

Windows 10 64bit, Intel i9-9900@5Ghz, 32 Gig RAM, MSI RTX 3080 TI, 2 TB SSD, 43" 2160p@1440p monitor.

Posted (edited)
If only binos were implemented for the charlie hog pilot, but meh... we got TGP and somehow, I'll post a vid soon of my runs from far away.

Have a look at my posting #4 again! >>http://forums.eagle.ru/showthread.php?t=79705

 

It's relative easy to map a button with a script that does exactly this.

I mapped the paddle switch of my cougar with a 12x magnification. - and the script turns on also the "precision mode" of the TrackIR while I'm in "bino-mode" - so it feels somewhat gyro-stabilized - and its much easier to examine a particular area.

 

 

Edited by PeterP

Posted
I'm not sure if this will help people but I put a page together to help people make good gun runs:

 

http://mildlyalert.wordpress.com/2011/11/25/gun-runs-in-dcs-a-10c-brrrrrrrrrrrrrr/

 

Using the edited snap view you can quickly focus your screen on the HUD like a pilot tunnelling in...

 

I find gun runs much much easier using this.

 

Very nice page. I also checked your Arma 2 blogs as well. Nice work!

 

Have a look at my posting #4 again! >>http://forums.eagle.ru/showthread.php?t=79705

 

It's relative easy to map a button with a script that does exactly this.

I mapped the paddle switch of my cougar with a 12x magnification. - and the script turns on also the "precision mode" of the TrackIR while I'm in "bino-mode" - so it feels somewhat gyro-stabilized - and its much easier to examine a particular area.

 

 

It seems that the trackIR_Z trick for zoom axis in the menu options does the trick. But I actually turned it off (unmapped it), together with Absolut longitudinal shift view. Now I have a unified zoom level.

 

 

I practiced gun runs using default zoom, at angels 6, 4 click away from target, and it somehow worked. I find the whole thing easier when the target stands out agains it's background(foliage, raw terrain) as opposed to being cowered in a busy apartment block junction... :thumbup:

 

However, I did a few runs the other day, and quickly withdraw that conclusion. The trick that was supposed to work, was the Gun hud Occult thingy turned on/off and just POINT TGP without lock on the intended target (to get a diamond only and no trailing designation). Either ways, the gun occult thing will obliterate the TGP diamond on either occult modes.

 

 

So my currently partially valid finding, would be to attack between angels 4 or 5, set proper DTS elevation, dim the pipper/hud (overall) a bit, and from 4 clicks in PAC only ( I could kiss the inventor of PAC for such novelty).

 

Also the trim issue with the campaign default loadout (2 AGM K and 2 AGM H, 2 AIR, 2 87's, rt. TGP 2AIM-9, lt. JMR) is easily managed with proper speed - VVI - ADI monitoring (or HUD VVI vs. aircraft datum).

 

But just out of curiosity, the manual mentions a 1HE:5AP = 6 Rds, for a belt of 1150, and for a gun rate 4200 rds/min. Is the part about warming up modeled (first 0.5 sec?/10 rd spew)? I now follow the principle of gun runs for targets in the open against sufficiently discernable and contrastable background. Sorry for the bold.

  • Like 1

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted

oh, well.. :thumbup:

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted

G00Dnight has it spot on afaic.

 

I sought out this topic because I found that whilst flying, I had severe issues trying to read what was written on the HUD. When I zoom in either with TIR or my zoom assigned slider, the text on the HUD stays the same size - and unreadable to me.

 

Funny thing is - I don't remember having this issue before. I could wear my reading specs - but my monitor is several inches out of 'range' and would be a blur. And no, my optician won't give me bifocals! I had severe iritis a while back (arthirits of the iris) and it really screws your eyes up long after you get rid of it.

 

I'm screwed. :cry:

Posted

 

When I zoom in either with TIR or my zoom assigned slider, the text on the HUD stays the same size - and unreadable to me.

 

You definitely mixing up "Absolute longitude shift camera view" with Zoom (aka changing FOV).

 

Use [KP/],[KP*] for zoom.

Posted

Ah, now I realised why it was illegible. I said it was okay before - and that's because I was using the correct HOTAS profile before.

 

Last night when I was having difficulty reading the HUD, I had my BS2 profile loaded. I had just jumped in to take some screenshots for LockOnFiles and forgot to change the profile.

 

I remembered when I started flying this evening. :doh:

 

It's my age, you see :(

Posted
You definitely mixing up "Absolute longitude shift camera view" with Zoom (aka changing FOV).

 

Use [KP/],[KP*] for zoom.

 

 

He should unmap Absolut Longitudinal shift view from trackIR_Z, and map trackIR_Z to Zoom View command. It is unassigned by default, and it is the first in the views list in Sim subcategory of the controls page, followed by Zoom in slow, out slow, zoom in, out, etc.. you can't miss it.

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

  • 8 months later...
Posted

Hi...

 

I use Free Track.

 

When I move my head towards to HUD, I can close the HUD, but symbols still remain small! Is that what you guys talking about here?

 

If so, isn't that a bug and why ED didn't fix it? I've just started to fly with A-10C, and it's very annoying...

 

Thanks.

Intel i7-14700@5.6GHz | MSI RTX4080 SuperSuprimX | Corsair V. 64GB@6400MHz. | Samsung 1TB 990 PRO SSD (Win10Homex64)
Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | TM Warthog Stick w/AVA Base | VPC MongoosT-50CM3 Throttle | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5 & M.Quest3 VR
>>MY MODS<< | Discord: Devrim#1068

Posted (edited)
Hi...

When I move my head towards to HUD, I can close the HUD, but symbols still remain small! Is that what you guys talking about here?

 

No, that's not the case here - its about forward shift of the View-point instead of FOV, aka Zoom, in FC3 planes without a cockpit that is designed for full 6DOF.

 

 

If so, isn't that a bug and why ED didn't fix it? I've just started to fly with A-10C, and it's very annoying...

.

 

 

Please make a little mind-experiment:

 

Imagine that the symbols in the Hud would get bigger if you lean forward ...

What would happen to a mark/nav point that is marking a specivic point at the ground?

Further:

Would you be able to hit a target with the piper when you move your head a little ?

 

 

Read/Google a little what a Collimated HUD is.

>>> http://en.wikipedia.org/wiki/Head-up_display

 

To make it short:

No, this is no Bug, it is the real behaviour.

Edited by PeterP

Posted

O-h m-y g-o-d-!

 

How stupid I am... I appologize Peter. I knew HUD (how to say) physics or rules. Just missed zoom thing.

 

I had no complaint about this while flying with Ka-50. Just checked Ka-50 HUD. Oops! It's the same. This is real... I can't get closer the HUD in Ka-50 either.

 

So as you said this is not a bug...

 

So now, my main question is that why I feel uncomfortable about closing the HUD in A-10C and don't in Ka-50. :)

Intel i7-14700@5.6GHz | MSI RTX4080 SuperSuprimX | Corsair V. 64GB@6400MHz. | Samsung 1TB 990 PRO SSD (Win10Homex64)
Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | TM Warthog Stick w/AVA Base | VPC MongoosT-50CM3 Throttle | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5 & M.Quest3 VR
>>MY MODS<< | Discord: Devrim#1068

Posted (edited)

No need to apologize!

 

Remember : It is never the question ,

it's always the answer that let the question sound stupid.

 

 

...and I'm just happy that I could help you to answer your own question.

 

So now, my main question is that why I feel uncomfortable about closing the HUD in A-10C and don't in Ka-50. :)

 

Don't know..., maybe readability?

Than try this: Big HUD Font for A-10C

Edited by PeterP

Posted

Thank you. :)

I think that's it. Slightly bigger characters. :)

Intel i7-14700@5.6GHz | MSI RTX4080 SuperSuprimX | Corsair V. 64GB@6400MHz. | Samsung 1TB 990 PRO SSD (Win10Homex64)
Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | TM Warthog Stick w/AVA Base | VPC MongoosT-50CM3 Throttle | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5 & M.Quest3 VR
>>MY MODS<< | Discord: Devrim#1068

  • Recently Browsing   0 members

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