Pavlin_33

Well, when you listen to US Navy pilots that flew the Hornets, thay say they were never allowed to go over the limit, in this case the "soft" limit as you have mentioned of 7.5G ( I made a typo in earlier post). They were not told to go over this limit in a dogfight or in certain situations, they were instead instructed NEVER to go over this limit. If the manual states the same (and the F/A-18 was modeled by it), then this should be the baseline and not some potential limit that is not realistic and/or sustainable. Again what ever the reason in RL might be. These kind of performance excursions in DCS should be high-risk situations, where you might be ok but most probably won't, and not something where you operate most of the time comfortably.

Well if the operational limit is 8G (for what ever reason) then it should be the a base reference. I mean, if an air frame can technically sustain certain load, but it's limited, DCS should reflect that. I mean it should not matter what the air frame could pull off theoretically or only one- or sometimes, but rather what corresponds to reality. Same thing we have with the Hornet, which is supposed to be a 7.3G fighter, but in DCS it's more like the Eagle. Us pretending that every air frame in DCS is brand new and disposable is not really realistic, in my humble opinion.

I am not sure what exact steeps are needed to reproduce this bug, but when starting cold-n-dark a false "BINGO" warning is displayed on the HUD and there are no way points displayed on the HSI screen even though they are loaded and present in the navigation list. Selecting a waypoint one, for example shows some bogus 1600+NM point. On my screenshot you can see both issues as well as the list of the entered points. My takeoff field was Beslan.

Fighting an AI plane, is completely different that fighting a human adversary. I feel it would be similar if we could "drive" the SAMs our selves.

Export version: Page I5, Figure 2. Speed vs max G graph.

I think it should be the same like Su-27 and F-15 for example: rated G, times 150% and that's it. Then everyone would be on the same page and we would not need to get into the whole metal fatigue argument. What we currently have is aircraft being rated lower G in the manuals, but pulling more G than some other platforms that have higher G limits on paper.

Both your PC and your tablet need to be on the same network. In my case I have a PC connected to the router via a LAN cable and the tablet via Wi-Fi. You can access the same interface from multiple tablets, just load the same address in the browser.

According to the manual, I have, it's 8G - not sure if it's because it's an export variant.

All IR missiles are fire-and-forget. They require no external guidance.

If we get proper GCI link, neither will 27T , matter nor the "crappy" (less capable) EOS. You will have a target on the HUD provided by the ground stations.

I would say prob not, since the speed did not drop that much, but I am not 100%. I am not sure of the track speed, but indeed I was very close eventually. Yes, the driver seems very competent, I agree. The thing is that this might not be the sniniest example, it's just the latest thing that happened. The worse one I have experienced so far was shooting at an A-10C in MP from low 6 at 1.5km and two R-27Rs missed along with 73s. The target did not maneuver at all, it was just releasing chaff/flares. That was the first time I realized that something might be wrong, but I disregarded it thinking it might be a desync or something similar. I will see if I can find a better example in the future. No track - was in MP

I guess a more straight forward example is needed. I will see if I manage to capture another one of these situations...

He was doing 446km/h true at 70degrees, which unless I made a mistake, is around 150km/h closure. What's the notch filter on the Flanker? My second-last 73 misses from left eight o'clock from 1.8km and he was not even flaring.

Well no, all those missiles are all aspect, and plus as I mentioned it happened also from low 6 position some time ago - not sure if I have a TacView of that one. Something is off here. No other DCS aircraft, that I am aware of, behaves like this. I mean, what were we supposed to do, perform a stern conversion at < 2km? Even choper can be hit, but not the A-10C. P.S. my last 73 was practically launched from 6 o'clock position

It's not the first time I experience this in MP, but only now have I decided to raise an issue, with SARH/IR missiles missing A-10 from point blank range. In the provided GIF from distance of 7km down to basically nothing, the A-10C manages to evade 6 missiles in total, with only mild maneuvering. Now before anyone jump on "he was notching" train, the A-10 was maybe notching the first 27-R, but the rest should have hit. I've had my missiles miss form dead 6 at distances less than 2km also, but I attributed this to possible de-sync at a time. In total the following failed to hit: 3 x R-27R 2 x R-73 2 x R-27T It's like the A-10C has a cloak of invincibility or something. It seems easier to fly over it and bomb it, then to hit it with A2A ordinance.

I am talking about the "red" middle light that flashes, a long with audible beeping tone, when there's a missile launch. Cookbook of the export version of the MiGgy mentions it only in context of "Nike Hercules" missile launch. It makes me wonder if other missile launches can be detected or not. I guess yes, but there's no mention of them in the documentation.

Well I kind of explained wrong way around. The 2Hz flashing red light and the beeping sound we already have when there's a missle launch. It's just that the manual only mentiones it in context of a Nike launch and nothing else.

It would be great if we could set up the SPO15 on the ground to classify different radar emiters.

Eagle has a huge bug where it can fly just fine when severely damaged by cannon rounds - burning engine, missing part of the wing. I am not talking about limping back to base, but rather still being to dogfight. It has happened to me in MP both as a target as well as an aggressor.

I meant detecting launches, as in 2Hz flashing red light together with "beep-beep" sound. I was not refering to the bottom row of lights that categorize the threat type.

Is it me or is the RL SPO on the MiGgy only capable of detecting missile launches from "Nike Hercules"?

No auto IFF on the real thing: manual button press, followed by up to 4 second ident period, but IFF in DCS sucks anyway.

Well, that should happen to any plane, but that's not how it works in DCS for other air frames.

All I'm saying is that F-5 has clearly higher tolerance than 150% (of max rated G), which I believe is the standard for DCS.

It was from a mutliplayer dogfighting server, so no track I am affraid. I also don't own the F-5, so I can't make a track. I am not so sure about that statement, at least from the consistency point of view. I am not aware if any other DCS module has these kind of margins when it comes to overstressing the frame.