microvax

I see no reason to do so tbh, Not having the INS running doesnt limit the Mirage combat capability wise in any considerable form, in QRA scenario it would be sitting on the ground with the INS aligned. So It basically just reduces the feature to navigate to waypoints without having to check f10 for that. How exactly does that anything else, but annoying the crap out of the M2k pilots. Also, if you are really scrambling, you dont have radar 1-3 minutes after takeoff anyways.

Honestly, given the odds stay that bad, yes please ! @crashO Well he launched from subsonic, which means he was even further from optimum range then you were. Obviously that is defendable. I just never launch over optimum range :D. I had people try in squad training for hours, against a medium to low altitude launched Super530d within optimum range one has pretty bad chances of defeating it kinetically, especially in comparison to memes like the r27 and aim7 which just basically stall of the rail ;D.

That is some next level hyperbole, I completely agree that the Super530D outclasses the r27r by a lot, but plox. Technically your statement is very wrong. But again r73 and r27t outclass the Mirages armament by simply beeing a category it doesnt have. If you get launched on by a Super530 just notch ot go cold. I loose like 40%+ of missiles to notches. Dont try to outmaneuver it. Simply dont.

Didnt touch emergency trim, but given we had workaround for bugs using actual system features "against" the bug, I tried that already. Doesnt work. Best workaround is switch it into ATT for a second, leaves you with a trimmed plane.

Imho the default delay should be 0, the available options are good though imho. For the user side which now and then hosts a Mission for a few friends the 10min is just something to reset to 0, while there is a lot less servers which would be able to set it to 10 min or more. :) For the problem of cheating using exports. Thats nothing that Tacview can solve I fear. The most sensible way to solve the export problem would probably be to just implement a serverside key generator, the client can manage them for each server, basically whitelisting clients without having to whitelist $dude for the 5th time because he nuked his config. In return it gets logged server side for each client which requests export auth, which exports were used client side. If there is $fishy things happening from the client side, admin can check what used the export. Simple[r] to implement [than custom premium API], no need for jesus complicated delayed data delivery on the server side. Every export using solution profits, Server basically just denies or authorizes the client to export stuff. And server admin can allow or disallow per player and in case of $fishy things can check what $client is using the exports for. Cockpit owners happy since they can be individually allowed, Server happy since its very simple task for it, Server admins happy since they dont have to believe $excuse, and solutions like the Tacview delay still work flawlessly since its completely transparent. I mean atm the traffic isnt even encrypted, so if someone really wants to, he can extract all the data he wants relatively easy anyways, but I guess the combination of "is capable of doing so" and "finds it acceptable to do so" is rare enough. But given the state of DCS multiplayer, from a technical standpoint, I am kinda pessimistic hoping for ED to do something about that, before the performance issues are fixed, although it would be way easier.

If you start from runway in the mission editor it seems like you got the supposed internal + external fuel as internal capacity plus the tank additionally. So If you jettison it after takeoff you still have the 100+% fuel.

=RvE=Flame =RvE= Egypt F15c =RvE=Tito =RvE= Bulgaria F15c =RvE=MicroVAX =RvE= Germany Mirage2000c (If no A2A slots are available, I would fly it with self defence armament only as A2G[if hell freezes over and the swedish thunderbolt will be there, I would like to fly that.]) EDIT:15-FEB 19:19UTC =RvE=Chico =RvE= Murrica Su27

A which bk90, B against what target. In MP they dont work at all.

The radar cant lock anything and thus cant direct aim9 or provide lead, just ranging. Its really only the elavation indication beeing broken by the looks of it. I can elavate the radar but it doesnt tell me how much its elavated, which is kinda hindering.

roggah. Lets see how fast chain of command over here spits out a few names for the leftover slots. :D

Which skin do the red side mirages have, there was a FF incident today and I want to avoid that in the future. I did take GCI picture as enough, but forgot, that damaged planes disappear from GCI view. x)

Sometimes the trim is not usable, then the pitch trim indicator doesnt move at all, neither does the plane behave as expected. Or one has to press the corresponding trimm controll like 30times to even get a single degree of trim.

Hi there ! =RvE= will be flying with 4 pilots again, names and corresponding frames are TBA. Edit: Well, due to wildcard signups not beeing valid anymore, here are our signups: [WIP] https://forums.eagle.ru/showpost.php?p=3051927&postcount=32 S! Question from me personaly: Does the no clusters rule apply to sensor fuzed systems only, or also to dumb clusters like the blg66 ?

For the the elavation changes, but the indicator states its neutral all the time. The air to air ranging just accounts for drop, not for target movement, but not sure if ranging works atm, didnt try that yet.

This would be very nice. Especially to find out where all the RBS15s go sometimes. Trying to hunt down some MP bugs atm but client tracks are like 99% [that hyperbole] corrupt.

RBS15s and RB04 are atm dying as soon as the launching viggen dies, this does not reflect the ASMs beeing independant aircrafts. Is there a plan when this will be addressed ?

Isnt the TGP only used on the av8b+ ?

that would be great !

Yes, MIX is performing entirely wrong on the MJ2 side, overperforming against heavy armor by a lot, meanwhile it is underperforming against groups of light armor. The pure MJ2 loaded BK90s are atm competely useless practically and are far from what they do IRL. Tbh I am fine with the situation until the MJ2 can be implemented properly.

Hmm, I know there is stuff missing, but in comparison to ECM, Radar, IFF, and kinda a better damage model for ground vehicles especially, proximity fuzes are a pretty trivial thing to model for ED. well I guess we wait. :D

Hmm :( thats sad. Its kinda hilarious that something like DCS doesnt support proximity fuzes. :D

Which one of their tones. For the SA3 there should be 3 for the SA6 there should be 2. That is also reflected in the ELINT entries for both. And the RWR actually distinguishes them, problem is the most dangerous one, aka the one which is active for STT has no tone.

For Airborne radars I get the alternating tone, indicating a very high PRF or CW. From SAM-Systems like SA15, SA6, SA3 I only get a fast flashing indicator on the CI, but no sound, as soon as the System switches from search to track.

Afaik the RB05 should have a radar proximity fuze with a radius of something like 3-6m. Atm it even fails to trigger sometimes, penetrating the target.

I mean the title is self explanatory, but here for completeness sake: In air to air mode, the radar elavation indicator allways shows a neutral position, even if that is not the case. This makes it very hard to estimates a contacts altitude.