hein22

Can anyone hear the AI speaking to the carrier during recovery? Or the carrier speaking to the AI? I have the correct freq set and the whole operation is done in silent and kind of looks odd. Did you experience the same? Thanks.

Also, what are the speed limits of navy patterns? I feel like I have very little information to simulate correctly these procedures.

So I watched wags "tutorial", and he talks about 10 mile racetrack... Where does that even come from? Are navy racetracks lenght defined by time like in civil aviation or by distance? I don't even know what each bank angle corresponds to which rate of turn. Manual doesn't say anything. Wags says that 300 gsd at 30° bank angle (I think) is a 1.5 minute turn, but that's all I got.

Haha LOL. Maybe next weekend? Did you watch my track from the ICLS bug report?

Hey Gripes! I didn't actually test many scenarios, only the thunderstorm that comes with DCS which has a "realistic" setting. Like I said on a different thread, pitching deck is less than before for sure, but it happens, and pitches quite a bit.

Attached a track showing AI conflicting with player on deck and a second AI plane that crashes into the first one. AI should detect player is obstructing taxi route and de spawn accordingly (as the manual says) so as not to create a conflict. Also, the hitbox of the superstructure is wrong and can be seen in this track should ED wants to check it. AI ignores player.trk

Yes you're right!! the camera is indeed very well stabilized. I guess ED forgot to do the same with the IFLOS. Maybe because two days from launching the module the lights were not even visible and then they fixed it right on time. Hopefully they know about all this stuff and are already working on them. I just wish they had put the same effort on systems like they put on graphics.

No, I think ED got that wrong and they even put it on the manual. ACLS has DMC, Deck Motion Compensation which has nothing to do with stabilization. A stabilized system shows the same angle in space regardless of the frame, this is what the torsion bar does. A compensated system guesses future movement to show the pilot the best angle to touch down and meet the carrier landing criteria of the given aircraft. IFLOS in the old stennis is well simulated and it shows the same angle in space, but in the supercarrier it shows whatever angle is created by the axis of the deck and the projection of the lights (wrong). ICLS was never stabilized in old or new carriers.

So this is a very interesting thread. I'm a certified IFR pilot IRL so I'm very familiar with instrument procedures. What we do not have in GA and CA is pushing times that are so restrictive and precise. In civil aviation we account for wind and stuff to have a proper holding pattern but all those techniques and mathematics are just approximations to a solution and very often won't make you have a perfect racetrack. Civil ATC will tell you each and every step you have to follow with times as well. They do not expect you to have a 10 second precision, not even close. So my question about this naval procedures, which I do not know, is how are you supposed to be on the fix at the push time after doing a holding pattern (1?) if they didn't tell you when you are supposed to begin that pattern? See what my doubt is? Like if I start the pattern at n time I will be at the fix at x time after doing 1 pattern, but if n changes so will x considering that the pattern is fixed. Thanks.

ICLS and IFLOS are not matching currently and IMHO due to a bug. But you have to take into account that their indications are indeed opposite IRL. A low ball is a low plane, but a low ICLS glideslope is a high plane.

Nor ICLS nor IFLOS stabilization is implemented yet. In the old stennis the IFLOS is stabilized but the ICLS isn't. In the supercarrier none of those are stabilized. SPN41 is mounted on a torsion bar. IFLOS has a whole system for angle projection in an earth reference stabilization.

Please mods don't take it hard on me for replying again, I'm not bumping but providing more information acquired just now. I found out that the root cause of this bug are statics. You can spawn 72 AI or players if you want when the SC is empty and it will run smooth. But if you have any static on a parking spot and at least one flight delayed (AI or player) then things go crazy (fps and parking logic).

Thank you for your support NL! I apologize if my interest in the product made me bother you. I will be more careful from now on. Stay safe.

Bump

Bump

Bump

Bump :)

Roger. Thanks. Take care and stay safe Santi.

Thank you for the details. Trackfile Memory has nothing to do with radar ageing setting, and that ageing setting is what is generating this situation. Additionally, TWS in the hornet isn't working like it works "good" in other modules so something is going on, right? Giving launch warnings, DT2 not guiding midcourse, L&S guiding when radar in ageing, etc. Sorry to put all my frustrations here.

I still understand it as before. Anyway, I did my part of testing this thoroughly and report the issues here. It's in your hands now, I hope though you can make TWS work some day. Thanks for the support.

I even attached two tracks showing the issue perfectly. Please watch.

No, no arbitrary point, it guides exactly to the target as long as memory is long enough. Test it with 32 seconds in radar data page and see it for yourself.

Forgot to say thanks, sorry! Thanks BN.

Sure. If it helps I put the whole system just in case. CPU: i5-8600k - GPU: GTX 1070 - RAM: 16GB DDR4 - MB: Gigabyte Z370 - SSD: WD Black SN750

Yeap, you're right. However, how sure are we about how it should work in that regard? Maybe signal intensity isn't something the RWR wants to show the pilot. Are we certain that IRL it is that way? We'll never know.