pchRage

Simple SP test mission. Caucasus default setup... no wind, 25k AGL, S to N flow to a STP ~60nm away. Full mil starting at 0.8M. Set auto-pilot for alt/course and observe.. Same load-outs for F-16 and F-18.... F-16: 2x120, 2x9x, 4xJSOW-A, 2xtanks, tpod, no pylon center, no hts F-18: 2x120, 2x9x, 4xJSOW-A, 2xtanks, tpod on center F-16 continually loses speed and increases alpha till its at a paltry 0.67M at the stp. F-18 accelerates to~0.93M by mid-distance and maintains to the stp. I know its sort of apples to oranges, but I wouldn't expect the F-16 to fall out of the sky. I basically must use at least min AB to maintain speed... The only way to get close to the same speed as the -18 is with only 4xJSOW, no missiles, zero pylons...completely clean.. and even then.. its 0.90M not .93... In order to not fall out of the sky, I can swap the wing tanks for a center tank and leave everything else as originally tested... that will at best hold 0.80M... Maybe this is completely accurate and you just cannot combine double load jsows with wing tanks... testJS.miz

Any comment on this? It's pretty challenging for F16s against other modules already...but when you finally get to a perch with the T/W E game, its very hard to cash it in due to having to eyeball the shot with just the gun cross and funnel as radar is out-to-lunch.

Thanks for the feedback, what you are saying does describe what appears to be happening. So.... does ED consider this ACM behavior a Bug or Correct-As-Is ?

Simple SP mission. F16 flowing North with a kc130 off the nose same direction and another kc130 flowing 45degrees towards the NW. same alt. Turn on HMCS, switch to DGFT mode... slew helmet to kc130 that is flying towards NW away from nose. Now TMS up to activate radar ... locks up target in hmcs oval... TMS up again... now the kc130 off the nose is locked up even though the HMCS is still pointing at the other target. TMS Up again.. picks correct... Up again... incorrect.. seems to keep toggling 60/40 between where the HMCS is looking vs straight off the nose... Bug? As-Designed? Operator-Error? Attached mission and track: ACMHMCSTest.miz f16hmcs.trk

Last I heard it was know issue from at least this summer of not even earlier. Is this still in progress, still considered a bug, or as-designed? Simple test SP mission. player at 20k, kc130 at 10k, over water (zero ground clutter) head-on. Simply activate ACM guns mode, roll over and attempt to acquire. Zero success in f16. Attached is the mission, and 3 tracks (1 for F16, and an F18 and F15 for "comparison"). Thank you. f16.trk f18.trk f15.trk ACMTest.miz

Thank you for the great details @Frederf! I didn't know GM could do both, just with a blurry image factor on movers. Is it also "expected" that in SEA mode, the TMS Up does nothing and EXP doesnt show at any range or just EA issues?

I have a 3-ship of ...ships... big cargo tankers moving in a straight line at 17kts. At 40nm the SEA mode radar sees nothing. At ~20nm it see's a single dot. If I EXP.. nothing shows up. If I try to TMS UP, nothing happens. If I try to hit TGT having the cursor centered on the ship, nothing happens (probably because I couldnt bug target). I redo the test using GM mode.. and it sees the ships in Norm/DMBS1/2. I can TMS Up, TGT, etc per normal.... BUT.. why would GM be able to see these ships MOVING at 17kts?

@BIGNEWY Can you please clarify if the pylons should/will separate with the wing tanks? thx!

During BFM or other heated maneuvering, I am inadvertently twisting the 18 stick left/right. I double checked all the bolts and even took it apart to make sure any internal bolts/screws were secure...they are. The metal locking ring is also firmly clamped to the base. What I realized is that the metal shaft that is "friction held" by the locking ring is not strong enough for my bad hand/eye coordination Has anyone had the same issue/come up with a solution? I dont recall the warthog stick having this issue either...

Is there any eta on this?

"....Then I’ll over G the targeting pod with a smile on my face" https://www.allthelyrics.com/lyrics/dos_gringos/im_a_pilot-lyrics-1249184.html

I wanted to post this in the DCS 2.5 controller bugs area but its closed and said to post in individual module..soooo here I am... If I bind the General -> Frame Counter to a button on controller... it doesnt work... doesnt toggle the fps info at all. If I change the keyboard binding to say, RShift+PageUp (unsed), it doesnt toggle either. Even after I remove the LCTL+Pause entirely, it still responds/toggles to that key combo...

ok now I get what you are saying... I went with that first screenshot I saw that was PLUS.. not MINUS.... swapping to MINUS and it makes sense the force needed for pure (black line) pitch!

Am I missing something here? I tried out the 12deg in the RS software, and its great/more natural.. but Windows and DCS do not seem to line up. Ie DCS is using actual position vs being purely pitch with zero roll...

Fyi, i turned off MSAA and the problem is gone. Did a 4 hour night mission with and without nvg and no issues. Ive also increased the steamVR SS to compensate for no msaa.

Maybe a bug, maybe I'm doing something wrong... Turn on main power Request ground crew to turn on Ground Power Setup jet, align, stores, etc etc (Leave FCR switch OFF) Start engine routine Request ground crew to turn off Ground Power Turn on FCR Nav mode, FCR working propertly Switch to MRM mode.. FCR stuck as "off" in MFD Switch to Dogfight mode.. FCR is working properly Switch back to MRM mode.. FCR still stuck "off" Double click osb on FCR and replace it with something else.. WPN, TGP, etc mode Double click osb again and select FCR FCR is now working properly This only happens when I use ground power... normal startup from engine, no issues...

Back n forth Sounds like optimal case... slew hmd with cursor depress to start getting tone. stop/slow maneuvering to avoid seeker los issues. uncage, fire..

I will certainly test the roll aspect.. I do not think I have a clear answer on "yes" you must uncage vs "no" do not vs "doesnt matter"...

Great!

Thanks for the feedback. @kengou what do you mean by "more reliable" though?

Recently been having mixed results when firing an Aim9 under radar quiet scenarios in MP. I have used just cursor depress, align hmd to target, get a tone, fire and splash. Other times, same situation and it just goes ballistic. I have used cursor depress, align hmd to target, get a tone, THEN uncage, fire and splash. Other times, same situation and it just goes ballistic. I cannot tell if the uncage step in this scenario is necessary or not. I cannot tell if it is truly helping as my guide vs ballistic doesn't greatly different in either case. I'd say my ratio is 70% success in tracking in either scenario...

Buzzer1977 that's exactly the issue I started having about 2 weeks ago! Seems to only/mainly be the right eye in my Valve Index. I've narrowed it down in my F-16 when my lights are in flash mode, all on, as well as when the cockpit flood light dial is rotated past 30%. Night missions are pretty painful, if I get near wingman with their lights on, or taxiway signed it gets bad (NVGs tend to reduce it though). Also happens in daylight with external lights but less often. I also have a hard time recreating in SP... MP easily, whether I'm near another pilot or empty server... I've tried the last 3 versions of nVidia drivers, all same result. Even tried their new (2 day old) hotfix release... same with wiping shader/fxo, etc areas per normal update routine

Any updates on the throttle throw and/or "stiction" improvements?

I had the same goal, and solved it easily with the TUSBA. You can "create" a DX "button" based on the position of the throttle (as well as the ant, rng, cursor, etc...just havent found a reason to yet). 1. Put the throttle where you want position wise (ie at idle or near idle) 2. Select the DX17 dropdown and select Throttle 3. "flip" its direction (as/if needed) by clicking the little icon next to the dropdown. 4. Save setting (File -> save) 5. Reboot for good measure (sometimes after saving tusba, windows stops recognizing device calibration till I do a full shut down/unplug/replug...) 6. Then go into DCS and in the button mapping, find the idle detent... double click it on your tusba column and when move the throttle in/out at the base and it registers the DX17 button 7. BE CAREFUL. I have several times thrown my plane into idle cutoff during BFM and had to relit... which then loses all INS

I agree darkman222, but we also have a boresite and funnel that do not need radar... Usually the locking issue is high aspect related and in that case, just go for broke, dont worry about the overshoot, and just fill your hud with their plane, trigger down, and you'll hit I swear I think the bug may be that its locking where the shadow of the plane is...