dolfo

Old instruments do drift, you have a fast erect button next to the ADI should you wish to correct it; just note that the photo posted looks about right, ADI consistent with visual horizon and radar horizon. The standby horizon is left caged in the photo? There is a red flag showing.

I do not have anything factual to contribute, but: I do remember F-5E pilots mentioning effective air to air cannon range to be just over 1000ft; it was mentioned 3000 would be a nominal max range but the large dispersion made it improbable to get concentrated hits on anything at that range. M-2000 drivers had incredibly accurate air to air cannons. Some (most) would intentionally aim for the connection between the banner and the tow plane, and it was said to be easy to hit (but terminated the exercise for the day). Of course F-5E drivers also did shoot the banner away on occasion, but it would either be at close range or a lucky shot, M2K drivers could produce it on demand until the CO told them to stop being funny and promised to discipline the next perpetrator. Anyway, I know none of this helps. But I think there is a chance the F-5 cannon dispersion might be just correct as it is - even if the specs in some books promise better performance.

I have done controls setup both sitting on the ramp and flying. Try single player maybe? Can't offer much more. Good luck.

Try opening the control setup during flight. Works for me.

From memory: Pal is preset channel Pal+G is preset channel + Guard reception F1=? H should be for homing, or direction finding? AR=stop, off. Might be all wrong too.

Why not? Should not be difficult to implement, and if people do not like it, they will not use it. As for "fracturing the community", I prefer to think of it as a meeting place for like-minded people. Sure many could prefer mixed settings servers, just as some people like or dislike labels, map options etc.

I never thought of it as a bug... seems to me the oculus is trying to tell user that his eyeballs are on the verge of being cooked and should be given a rest.

'HiTech' I'd say M2000. If you are willing to try older stuff, F-5 is fantastic.

Very true. Also, real world skies are not always clear. Visibility, lighting, contrast can make an airplane pop against the background and easy to see at 30 miles out, or impossible to spot very close in. I tend to justify the VR visual limitations to myself as chalking it up to a bad sky day. Would be interesting if that could be imposed to all players (VR only server).

It sure is a challenge! There is no advantage other than the immersion. But it is fun. :)

It is great fun, but comes with restrictions. PD 1.2 helps a lot. Can't go back to 2D flying even if it gives an "advantage" regarding image sharpness.

I sure hope someone is working on releasing the F-105 for DCS. Sure purchase for me. Do not know if it was mentioned yet, but there is a great book on the subject. Suggest people do a search for "When Thunder Rolled" by Ed Rasimus.

Happened to me too. I then uninstalled tacview and srs, deleted the export lua, re-installed SRS. After checking SRS working, re-installed tacview. Worked for me.

In my experience (not much to speak of) after the first spawn all groups get dynamically generated names. Some mission attributes are preserved, as general task, some detailed parameters are lost (ROE, for example). Might be wrong though. Good luck with your quest. -edit: actually I think clonegroup was preserving the original task, with respawngroup I had to push a new task? Away from the computer for a few days, can not check.

It used to work for me. to keep it dummyproof, I would ensure guns else PCA, magic else PCA is the command setup, not guns select magic select. Also I would check and ensure I have selcted the 530 in the PCA with switch in center position, then test if it works. Can not offer more at the time, hope you can sort it out. -edit: did not use target, just in-game control setup.

I think I have mine on 3-pos switch abstractions, fwd=gun else pca, back=magic esle pca... Surely someone will chime in before I have a chance to go home and check.

Happens occasionally to me. After fiddling with it for a while, it works. Then happens again. Annoying for sure.

Would be fun. Any version for me.

Yep. 30-ish degree dive, designate, hold release consent, pull up. Most of time release happens at 17-15 degrees nose down. Solid hits on designated point all time.

Dead accurate for me with zero wind... Dive angle too shallow maybe?

Same here.

As I understand compressor stalls are not fully implemented. It seems to be possible to carelessly handle thrust levers at high altitude witout ill efects.

Never flamed out at MAX thrust, just as advertised in the T.O. Thrust does deteriorate when IAS is low enough, as per T2 sensor and T5 modulation it seems.

The supersonic zoom climb profile described in the T.O. 1F-5E-1 Appendix I page A8-22 works for me. Can get the F-5 to 63000ft+ according to Tacview, just can not stay there... As already noted, not really the edge of space.

Can not comment on what other people are experiencing, but this is what I have seen: I think I get most of my tire failures when making abrupt use of rudder at high speeds. Out of trim and poor rotation do not help, also. Willing to accept that I may be inadvertently tapping the brakes too. Side loads on tires at heavy weight and high speed do sound like a good reason for tire failure to me. Willing to accept it as pilot error due to less than perfect technique.