theinmigrant

Thanks. I tried masking the pod and manouver hard and when the pod got unmasked it was right on the exact same spot as before. I wonder if not having INR implemented yet makes it cheat, maybe? I thought that not having INR implemented would have made the pod not being able to "remember" the last spot at all.

No, Wags did say that tracking moving targets was possible as of now. What does INR do actually, cause we have now a MEM message when the pod is inertially focusing on last point.

The hotas fov button now changes the MAV F FOV when the TDC priority is on the TGP. Track attached. Hotas FOV TGP MAV F bug.trk

The MAV F whot/bhot pushbutton now changes the FLIR like the TGP. Track attached. FLIRMAV F bug.trk

When you use the EXP function in the SA page the radar stops picking MSI on radar page. Track attached. SA EXP radar bug.trk

I know. I never tried AUTO to be for pinpoint strikes, I'm not one of those players that think a mk82 should hit an ant. But as a pilot I would like to share what I think. And what I think is that if the bombs dropped in AUTO always miss their target by the exact same amount of distance and the exact same direction of the target, then the logic dictates that there is something wrong with the code. I hope I dont touch a nerve here or make ED angry, this is what I think, nothing else. salute.

I do have the same problem. AUTO mode isn't accurately modeled IMHO. Me and my friends talk about this often.

If it helps, I can confirm this behaviour. Additionally if I may, I would like to point out that having the half circle hafu in the hud only for two source positive ID is not only not realistic but inconsistent with the way the ROE is coded as Wags explained. If the radar (due to current ROE) identifies as friendly only with a positive mode 4 and no other source, then the hud should reflect this. I hope this helps. Have a nice day.

Guys, also take into account one thing that is not realistic and perhaps should have been addressed by now: The fact that when you go into STT the PRF stays in whatever it was at the time of commanding the lock. This often makes a lock to be lost for instance due to being very far (like 75nm) and stuck in MED prf. If you change the PRF to HI during the lock and before it is lost then the lock is retained. As far as I understand and was taught, any modern radar selects the best PRF for retaining a lock when commanding STT.

Maybe its time for a track? I can't this week but it'd be good for ED to have one.

Cool thanks! :thumbup:

Oh ok, thank you. I guess I was suprised to see the word "closed" in his sentence. thanks bro.

According to this post from Nine Line: https://forums.eagle.ru/showpost.php?p=3968739&postcount=75 Were we supposed to get an OB update today? I know things can go wrong, so just looking to see where we are standing this week. Thanks.

The needles are the same in both helicopters so we're good. So you say that RL pilots do freewheeling checks with fuel cutoff? That doesn't seem right to me. I can be wrong.

So how do pilots do IRL to make a freewheeling unit check? All helos I've flown had that procedure in checklist. But I've never flown a fixed shaft engine like the Gazelle, only free turbine ones (that's why I assumed before this was one as well). I guess you could throttle down without letting RPM to drop below clutch disengage threshold and that way we should definetly see a needle split with the short arrow always ahead of the long one. If they dont split or if they split with the long one higher than the short one, then the freewheeling unit is broken and the helo must never leave the ground or the simulation is incorrectly coded.

Ramsay, can you check for me if the DCS Gazelle simulates the freewheeling unit? For example try reducing the throttle suddenly and check if you see the needles splitting.

Ok, I didnt know about the centrigugal clutch. Thank you for bringing that to my attention. I will investigate further.

Are you serious? I don't want to be rude, but it looks like you're not reading any of my posts. I know it writes TURB, and I explained that When I say compressor RPM we are talking about the compressor TURBINE rpm, so TURB doesnt mean anything. Either way it's modeled incorrectly

I'm not sure you know what a turbine is or how many turbines the Gazelle has. What I described stands, it is not arguable as it depicts Helicopter engines IRL. It doesn't matter the guy follows or not correct procedures. The behaviour isn't correct anyway. When you say turbine RPM, do you know there are two of them? Which one do you refer to? A turboprop engine like the Gazelle usually has a compressor, a compressor turbine and a power turbine. The tachometer MUST show power turbine rpm and rotor rpm. That's how it is. If the DCS Gazelle shows turbine rpm then it isn't modeled correctly, if it shows compressor rpm then it is not showing what it shows IRL. Either way it's done incorrectly.

Ok, I just saw in this video that the engine is not correctly modeled so I'll hold off for a while until it gets more love. Explanation: the long needle (N2) is ahead of the short needle (NR). That could never happen IRL due to the way a helicopter is built. The only thing that I can think of is that Polyshop coded the long needle to show the N1 which not only isnt how it is IRL but it would not make any sense either.

I saw that thread and subscribed to it as well. But they never mentioned anything about the freewheeling unit. I dont even think they know the bug exist.

Interesting. You have any information as to why is that?

Yeap, not a big deal though but it would be nice to have it fixed :)

No, I mean the freewheeling unit. It is a sprag clutch (or other solutions) that prevents the rotor to drive the engine or in the Gazelle case the power turbine. Can you split the needles in the dual tachometer if you throttle down suddenly?

Yeah, like I said, it only works if total engine is loss (or fuel is cut off), but it is not modeled.