DrGarantia

Exact same issue, with or without the radar the pod shakes like crazy I just got the module and tried an air spawn with the pod and had this issue. Both MT or ST versions.

Is anyone able to remove the visor in flight after the last patch? I can put the visor down, but pressing the button again does nothing once I am flying.

Any progress on this issue? I could provide some tracks if needed, but they are quite big since it takes a while to happen on MP.

What MAV search means/do?

I know this thread is not about workarounds, but there is one that works perfectly. Need to use a custom curve and the first bar in the curve should be at 87%, this is the point that separates ground idle from air idle, so if you are in the ground as soon as you move a tiny little bit it will move straight from ground idle to air idle. No range loss on the throttle. For the other bar just divide 87/10 and fill the numbers for a linear response if that is your thing, ignore the rest of the curve in the picture, I kinda need a dead spot on the range so I don't waste time trying to nail MIL on my TM TWCS.

If I remember correctly... The delay is because of the different position between the ground and air idle, you can see on the controls overlay that it won't go all the way back in the air. If I am not mistaken there is a mechanism that only allow moving it all the way back with weight on wheels, in the air it won't allow you move it back past a certain amount. Another problem of our physical controls not being a perfect emulation: if you bring your throttle all the way back in the air during the landing you won't engage the ground idle after touchdown, increasing runway stopping distance, you need to either go to idle after touchdown or wiggle it a little bit after touchdown so it will engage ground idle.

Any news on this bug being worked on? Got the Mirage recently and this is happening every time I play the mirage, for the first 20m or so of the flight I can use the radar altimeter, after that as long as it is on my frames drops from 60 to 12 until I turn it off. And the off/on thing doesn't fix it for me, need to get a new plane for that.

Same problem with the yaw SAS here, only play MP and can't really post short track since they are all huge files. Happens 100% of the time after 15m flying or so in MP.

Same problem, also 24gb of ram. FPS Drops to single digit while the game is uses >20Gb of the ram while on previous patches it would stay bellow 12gb most times. I know that this phrase is used a lot as an exaggeration, but on my case the game is literally unplayable on this version, I can't get consistent fps for more than 10s before it goes back to <10 while windows keeps writing GBs to the pagefile all the time.

I tried flying low to evade some SAMs this weekend twice, both times at around 30-40ft the plane is sucked to the ground, can't say if it is stronger than before, at least the effect is still there.

Yesterday I couldn't hit a single JDAM, most of the time they missed by almost a kilometer or so! Release 4 in sequence on the same target, at 10k ft above, they all hit further ahead and on almost equal spacing, there is something wrong with them for sure.

Can you lock on another aircraft with that? I only know about ground.

I wonder if there will be a new flight model for the JDAM, and if those happens they will apply to the A-10. Compared to GBU-12s the JDAM fly a lot slower for some reason, like it has a much higher drag or something.

Exact same problem, hud was OK before patch, now it is almost opaque with this green tint.

I am using a small macro on Joystick Gremlin on the pinkie button on my throttle, I use it for a few macros so another one won't hurt. For those who want how to make it work: On your button of choise create two basic macros. Both will be 3 actions: - vJoy Button "x" - pressed - Pause for 0.05s - vJoy Button "x" - released The first will have a joystick condition: - activate if (the button you are using) is pressed The second will have a action condition: - activate when this (virtual) button is released Just assign the vjoy "x" button you are using on the macro in game for " throttle range". You also need this button assigned to something else, because you need to press it once on every new plane since the game start with the full range enabled. It will work exactly like the hornet after that :)

Happened few days ago to me, twice on multiplayer, If it happens again I will remember to post the track here. Both times, happened when starting the right engine, both throttles were at idle, but the right engine behaved like it was in pushed into AB right after start.

Any news on steam release and price? I would be great if it is there next week, since there is the lunar new years sale.

Thanks, finally found a use for the throttle axis on the T16000m now :)

Is there one? I can't find an axis or a button to control the HMD knob anywhere in the bindings.

I use a TM TWCS with the attached curve on it, the important bit is the rightmost part. That might help your issue. I get the lower ground idle with the throttle fully back (100 in the scale) and as soon as I move it jumps to around the air idle (87 or so), there is not any significant amount of thrust in the 100-87 range to bother having it and I can still taxi as slow and precise as I would ever need.

Any news on this topic? Thinking about getting the F-5E and I absolutely love the F-18 feature that only let the engine go into AB if I held a button.

Yes, that is what I am doing, switch IFFCC to ON after changing to CM, then switch it back to TEST for changing back to HEI. That is only if you set ammo as HEI in the mission editor. When starting with CM you just rearm with HEI and change from CM to HEI and it will work, I think that is why maybe nobody seems to have noticed this issue before, I am probably one of the few "weirdos" that load the A-10 with HEI in almost all missions :music_whistling:.

Found the problem, it only happens when you start with HEI ammo set in the mission editor. Basically, the default HEI pipper you get is giving the AP shell impact point instead of the HEI point, the picture bellow explains how to fix and reproduce the issue. Why would I get 1m from manpads and ZU-23 in the first place? The whole point of using HEI ammo is to get those, and trucks, from a safe distance, not really a tank busting loadout but much more adequate for the missions I am flying right now. :thumbup: Never really tried CM at those distances to be sure, I would expect them to just harmless bouce and maybe scare some birds here and there :lol: edit: oh, btw I am using 3-4nm just as exemple to exaggerate the difference between the two shells impact points. 2-2.5 is working great against soft targets so far.

That was what I did. Changed in the ME, thanks for the info and the link, I think I found a bug, gonna do a few more testings just to be sure. If I chose in the ME the ammo type as HEI and then spawn on the ground or in the air the problem occurs, the new piper is in the AP position. If I instead chose CM in the ME, or just leave it as is the default, and then request a rearm on the ground for HEI, then change the piper it is on the right position. Just need a few more tests when I get some free time to be sure. So far spawning with CM, rearming, then changing the IFFCC seems to work, while spawing with HEI it will always be inaccurate.

HEI pipper inaccurate? I am still learning the A-10C and having a lot of trouble hitting things with HEI ammo, rounds always hit short of the targets, with a cold or air spawn. If I keep the round type as CM in the IFFCC and use the lower dot to aim I get very good results, but if I change it HEI and use the now sole central dot in the reticle the rounds always hits lower than expected, at 3-4nm they don't even hit on the same postal code :doh:. All I am doing is changing the round type in the IFFCC or using the plane as is in case of a air spawn, is there any step I am missing? Does it happens with anyone else?