deadpool

We are united in that neither of us got any fix he had desperately wanted :-) I have no idea how ED orders the bugs to be fixed.

Everyone else will see tracers but you. Even from all angles and directions looking at the bullets. I believe this is because for everyone else guns are just always rendered with tracers. So if you're selecting something other than tracers to be sneaky .. don't .. ^^

And that's also - to the best of my knowledge - the reason why it's only over one eye for real. To keep the other eye 100% for spotting.

He possibly thought something along these lines: class ExamplePlane { private: 3DCoords[MAX_WPT] _waypoints; public: 3DCoords getWaypoint(int index) { ... } void setWaypoint(int index, 3DCoords waypoint) { ... } } class F16 : public ExamplePlane { private: 3DCoords[MAX_WPT] _TGPwaypoints; public: 3DCoords getTGPWaypoint(int index) { if ( index >= MAX_WPT ) ...; if ( _waypoints[index] == NULL ) ...; if ( _TGPwaypoints[index] == NULL ) _TGPwaypoints[index] = 3DCoords.makeImmutableCopy(_waypoints[index]); return 3DCoords.makeImmutableCopy(_TGPwaypoints[index]); } void CZTGPWaypoint(int index) { if ( index >= MAX_WPT ) ...; if ( _waypoints[index] == NULL ) ...; if ( _TGPwaypoints[index] == NULL ) ...; _TGPwaypoints[index] = NULL; //we have garbage collection, right? ^^ } void setTGPWaypoint(int index, 3DCoords waypoint) { if ( index >= MAX_WPT ) ...; if ( _waypoints[index] == NULL ) ...; if ( _TGPwaypoints[index] == NULL ) ...; _TGPwaypoints[index] = 3DCoords.makeImmutableCopy(waypoint); } } and thought: yeah, that should be fairly simple.

MiG29 the other day I didn't see on the scope until it was at about 30nm (hot) in the F-16.

It doesn't in the A10. So it certainly won't in the F16.

Oh .. symbology and TWS in this game's Viper is interesting. You need a magification glass to figure that out. Given that you pick targets up at 40nm and your closure rate is FAST for a good launch, you don't have much time. Hurry! :-D

Welcome to the Viper, my friend. It's a preliminary status of the TPOD and it is being worked on. Improving the TPOD was actually one of few points that are supposed to happen this year for the Viper. So you might still get the proper TPOD /CZ / Delta-slewing in 2020!

I don't presume to know what was specifically ask but I interpreted it in such a way that the question was: What does the ownship RCS has to do with the ownship radar dish size/power. It would only make sense if you put viper against hornet and if it's head-on then I guess they would see each other at pretty much the same range. If that was the question. But my answer is just a guess anyways.

Well, I had about 3-5° changes in flight vector from throttling up and down. But I guess that's not it. If you don't have a track file, could you make a video of it?

I think the hornet is planned to have it, too. So once it's on the hornet, you know it's a step closer to being on the F-16.

Have you reduced your speed before crossing the mountain?

premier SEAD platform in DCS? You mean the Hornet? With the HARM in the Hornet you apparently even get a box indication on your HUD where the target is (minus range). You just slew the TGP on that and then can do classic attacks. Essentially using the HARM as HTS.

The F-16s radar automatically switches between MPRF and HPRF automatically. We definitely have HPRF. But I am open for sources.

Page 10 shows that this isn't even about the AN/APG68 at all. It's about the AN/APG66 for the F-16 and the AN/APG65 for the F-18. I will try to find the 10% source.

Just out of curiosity. What have you "seen" in the golan strike video that told you the F-16 was being updated? I am not asking to be negative, but because I might truly have missed it.

The F-16 radar seems to have a hard limit of 20nm for cold contacts. If it really is supposed to be lower than that, I'll have to think the Viggen is better tasked for A/A BVR. Also the numbers I saw for the time being indicate a less than 10% smaller detection range for the F-16 AN/APG-68. Though I am not sure if it is the (9) version which we don't get, or the (5) version. I'm glad to see this solidified with sources, as I don't seem to find any reliables online. BR, Deadpool

Let's talk availability. The multiplayer community is on open beta. So if you want that, you have to go open beta. Now as for the your Early access you can buy when you want argument. That is quite true. The only modern jet out of EA is the Mirage2000. So that's the only one you could buy. Everything else is in EA. So if you want to participate, you have to buy EA. Thank you for explaining me the theoretical freedom we have here. Please have a look at the F-16 forum where forum posts with people that feel - I think very understandably - deserted and left alone get closed and/or moved. Yet at the same time you will not get comments on defects posts, so posts where you actually try to HELP ED do get a much slower response and you usually feel like you have to prove beyond any reasonable doubt that you're correct. I opened a forum post with a friendly plea to get some comment on the communication there, and it got moved away into the wishlist, without any comment. It feels bad, man. It feels very unappreciated. And if you want to have ED's higher ups commenting, you have to go to hoggit anyways.

My track file sadly seems to be broken after a short while and would be over 2 hours long in total. Sadly not useful. So, I can provide a track file if track file generation is fixed ^^

I asked for a bit of change in communications. (a bit more feedback on defects, etc.) instead of being fast mainly with closing or moving threads. But the thread itself got moved into wishlist and is now kind of aging there: https://forums.eagle.ru/showthread.php?t=280043

Normal overhead after a normal 2h training. Coming in high for reasons!

Sometimes if a missile goes pitbull, instead of getting the (M) on the RWR for the missiles radar, you will just see the launch platform (even if it's turned cold) appear as "I'm shooting at you in STT like a Fox1" ..

Please guys. If this thread ends up about that topic instead it's going to be closed again. I meant it honestly when I posted this and would like some response. So far sadly the thread was just moved to the wish list part of them forum without comment. And I am not trying to interpret that as an act of satire.

It's on the list of things I'd assume. Fixes in general that is. But the whole G-stuff seems to be more deeply rooted and I wouldn't bet on it being one of the first things being fixed. It got reported in October 2019: https://forums.eagle.ru/showthread.php?t=252826 Negative G issue was adressed here, January 2020: https://forums.eagle.ru/showthread.php?t=260319

Just a bit of feedback for the moderators of this forum, without any emotion attached to it: It would be nice to see the same level of engagement and reaction time in the defects portion of this forum than when it comes to closing threads in the F-16 forum where people give into their sadness and disappointment (that I think should be understood by all involved here).