microvax

Not working atm: Target approach 10m Symptom: Missile allways sea skimms Boundary for area search. Symptom: Missile still goes for the closer target in single target mode, even while that is like 3km outside the boundary. Altitude after bx6: symptom missile allways goes 10m over water multiple target a: Symptom missiles turn 90degrees away after probable target aquisition Bearing search: Missile still goes for the closest target to the bx8, even while that is 10 degrees furter away from its flightpath then the target straight ahead. Course change: Missile self destructs after 90 degrees of turn, even on terminal. Address 84 cant be tested properly, since the area sizes arent known. But I suppose they do not work, since the corresponding search altitudes of 10, 15 and 30m cant be observed. The missile allways searches at 10m.

As said, setting angle jump or group mode in mission editor doesnt take effect in game according to both kneeboard and test firing.

Thrustreverser toggle, like one binding switching between armed and not armed, like with gear, would be surpreme !

In the Manual it is stated, that search altitude will be 10, 15 or 30 meters, depending on the search setting. I literally tried all search settings and all lead to 30m search altitude. Which parameter combo does give 10m search altitude ? Also it doesnt seaskim after descent point, even if ordered so.

No same Issue here. Cant get tracks displayed, also with a S type destination selected no fix preparation is shown [range and bearing from self] like in mal. Also cant clear any reconaissance targets by pressing rensa.

I completely agree here, 70 chaff is way to low, with 70 chaff nobody is going to lay chaff corridors like the BOZ100 series of pod is capable off. It is probably not as high as the standard BOZ100, but the ballpark of 70kg of chaff is probably correct considering the weight of the pods and they are based on the same origin. Unless each chaff packet is 1KG that doesnt really mix well. :D

Yee, Mav told me the same already. :D Tbh I am kinda glad myself that it didnt work out as intended, in the end, since it was not aligned with the intentions of the event. While I get that its obvious for people like you guys, playing DCS like since forevar, that such a rule is likely in place, for me it simply wasnt, due to me not having the experience in theese events simply. :D I am playing DCS since late feburary 2016 and first touched Multiplayer in Blueflag R6 in May 2016. GM3 was pretty much the only event I did observe from start to finish, missing the beginning of GM2. I guess I got heavily influenced by striking before hostile CAP even is a thing or even can react in the target area in Blueflag and the early strike on GM3. So yeah greenhorn lack of experience and no brief about it => AIM120s in cockpit. :D @turborush: Ah yee. Get what you mean. :) Happy to improve on that though, now that I halfway know what to expect ! :)

If anyone hinted to my failed undertaking during the first minutes of Redflag, that was no kamikazee action, in fact it was a polished to the limit timeplan. Problem was I didnt know of the Aggressors starting first and well, that ruined the 90 seconds safety margin I had originally included. FYI matching wheels up times would even with the realworld event times would have led to me beeing gone cold mach 1.3 on the deck 70 seconds before the first Aggressors got within 5NM of the target area, so roughly 20nm separation in a mach 1.3 chase with about as fuel reserve in full burner as the F15 can even carry internally at all. I regarded that pretty safe at the time. :D But well shit did hit the fan :D. I am indeed the only mirage pilot who can claim to actually have damaged or destroyed anything. 8-) 2,5 shilkas yay. :D Now for le such F-pole discussion. As maverick said, its straight naiv to believe to have the same chances in a Mirage against a F15 headon BVR. To make a rather long story short, planning any maneuvers in a Mirage VS whatevar scenario is a little risky since fundamental FM changes are still very much a thing and that broke at least my entire repertoire more then once. And tbh I do not regard the Mirages strength in the atm by flight model changes, rightfully so, very much threatened dogfighting reign. That is fun and all, but at best dangerous AF in the end. The mirage in DCS shines in sutained burn times, range, as seen, fast deployment to location X, Navigation, turn around times at base and radar auxiliary features. Its TWS might only be single track, but the option of a bullseye referenced TDC practically makes it possible for you to go makeshift AWACS, the waypoint integration makes it very much possible to achieve really good search results even from extreme altitudes even at close range, because one has a reference where the one has to search at what altitudes relative to range. The time on waypoint functionality hopefully will be working in next redflag, so accurately timed pincers can be setup with reasonable workload. All these features require very different skills from using superior weaponry and naturally are lot riskier to use, since their appliance usually comes with a plan to stick to and if that fails due to whatevar reason, there is the aim120 entering your cockpit unquestioned, while you are thinking that aim120 should be conceptually not be closer then 20NM sitting on a hardpoint of an F15, while you are cold at mach 1.3. But imho that is no good reason to downgrade any of the birds. More a reason to upgrade on how we plan to achieve things. I would be happy to see Redflag develop into a more complex battle scenario where a plan including various frames and interleaved operations is a necessity, not an option. :) And there is radar shadow on NTTR, I can tell you that much ! :D Enough that my next plan is already on the drawing board ! ;D

yes. BER -> NAV earlierst 2min before takeoff.

I have to emphasize that any concerns could be addressed already and the event organisers couldnt really be more reasonable listeing to constructive feedback. Really looking forward to the next event and the whole series developing over time ! :) S!

Okay I mostly cleared my concerns with Maverick in twitch chat already. The ahead start of the Aggressors was nothing I expected due to my research into previous DCS Red Flags and the briefing info. Thats why I expected a start on unpause like in other DCS events. So that on ground performance actually is a impacting factor. Maverick stated that it was intended that the aggressors get a ahead start and will be like that in all following events. So my feedback would be to make the starting conditions clearer, so that mission planning is not wasted because of unclarities like this. For the part of me dying during my strike: In accordance to my expectation of a start on unpause and aggressor aircrafts over the target area times relative to mission start from recent Red Flags I did actually start doing such a strike plan. Then I did training to optimize for scramble times. In the end I got startup procedures flightplan and attack plan trimmed down in a way. that The Aggressors would have to takeoff within 3 minutes from unpause to intercept me before deploying all a2g ordanance and within less then 1 minute to prevent the destruction of their shilkas, assuming from takeoff going 400kts ias to 20 000ft and going full burner as soon as I am detected. I also did backup planning for failed or no INS alignment, and especially I did make a table which tells me how much of my attack plan I am going to be able to execute depending on what location on my ingress I get the first nails. Shortcomming of my plan here was expecting equal takeoff times. Because I pretty much expected that start on unpause may not happen and instead a start from taxi would happen. So since I got RWR indications at the earliest possible time I scratched my last shilka run and the gun runs on BRDMs and BTRs. Again expecting equal takeoff time. I got STT once I pulled up from my first drop, aligning for the first run, I did expect that, scare le target and stuff. Then pulling up from the second run I knew that i should have time to do one more run on the northern group from east to west, extend heading 100 full burner. To make sure my plan holds up, I flicked on a2a radar during extend for lineup on last run. Thats when I got pitbull warning, while expecting still to have something like 30 seconds. I obviously went jettison all the a2g memez limiter off and turn cold but well rip didnt work. Edit: before anyone jumps to conclusions with my continious use of full AB. I did have enough fuel for full AB back to base giving me mach 1.3 at the deck escape velocity. I would even had that, if I have had the time to do a full strike, including 10-15% safety margin. The mirage has a ton of fuel compared to its afterburner consumption. For the moment I just thought I messed up, I overextended my time window or something. What indeed was the factor I didnt expect it to be was the early start of the Aggressors. Once I discovered, that the Aggressors got an early start I kinda did go bonkerz tbh. Spending 8-10 hours on Flight and strike planning and training. Testing options backwards and forwards. Testing for radar cover and escape vectors running different f15 setups on a plan, which would have worked if at least the synchronus takeoff criteria would have matched. At the time I still was pretty sure that wasnt intended, since Maverick after the server crash explicitly stated, when asking us not to join all at once, that getting to bullseye first would not grant us anything. Also someone who said he forwarded my concenrs to maverick that a start from pause was originally intended and got lost in the server restart. So yeah I went a little bonkerz there, obviously beeing annoyed that my precious plan did fail due to an perceived error due to the server restart. Given maverick said an early arrival at bullseye would not give us anything, I am pretty sure still that my attack was unexpected and I am happy at least that came true, and seeing that my timeplan would have worked out if the synchronus takeoff criterium was met also makes me happy that at least it wasnt the fault of my planning. Tl;dr So yeah, thats the story why that el retard mirage dyed early on. :D Unexpected starting conditions. And since I enjoyed the planning, training, and that it technically would have worked if the starting conditions were known, I pledge for a more precise briefing of what the starting conditions are. P.S.: Someone said during the stream the mirage is not intended for that kind of role. There is a correctish part and a very false part about this. It is true, that the Mirage 2000c is not an explicitly built for the role high speed interdictor. There is the 2000n though, which largely has the same fuselage and from which we also have the huge wing tanks. Its the high speed low alt nuclear strike variant. So while the 2000c has pretty limited a2g options in terms of accuracy and load, it is suited pretty perfectly for the high speed interdiction role if those limitations can be overcome. There was also a plan to take out Aggressor Aifield SAM systems that worked, I scratched that though, since SAM systems at the Aggressor Airfield didnt yield points. I will upload footage from my training and overlay that with the timeplan that happend somehow to illustrate the possibilities of high speed interdictions. I did hold that back until now to maximise le surprise effect. :D I thank 104th for hosting the event, I indeed had fun in the end and hope my input can improve future versions of red flag. :) S! EDIT: Here my really early go at the Aggressors airfield defense batteries. Again, would have done that with wing tanks and a 500nm terrain masked ingress route and had enough fuel for full burner home to nellis. But due to no points for base defense batteries and it beeing kinda risky I did drop that plan further along the line.

https://forums.eagle.ru/showpost.php?p=3020785&postcount=51 if nothing changes/changed, nope

Which you a smooth release as well ! :)

http://www.loneflyer.com/saab-boz-100/ The manual and current WIP releases show 36 flares and 72chaff iirc, the only info out there I can find about the BOZ100 is 540 55m chaff cartridges amounting to 80kg of chaff and 28 flares. Iirc that is also corresponding with numbers in the pre subforum aera viggen thread. I know that there are slight variances in the boz100 series. But A its same perdiod, the BOZ100 is just 11kgs heavier then the KB pod weight listed in the manual. So even if the KB we have only loads 70kg of chaff, that would be nearly 1kg per chaff cartridge atm. Which is pretty ridicoulous thought. :D So is that aspect still considered WIP or do we have better data basis which supports the CM composition atm ? :)

I agree, that the AI is playing a sensible role. But what method of stopping the AI from taking off do you mean ?

Arggh sorry for me beeing so blind. x) thx for le infos.

Noice ! Now that the mission is online practice can start. Two questions though, will the SAM network of Tonopah be published as well atm its not in the mission. Also, are the agressors limited to the NTTR in every direction or just the part that is pictured on the screenshot. [And muh mirage is missing on nellis atm, but I guess the plane selection will be hotfixed last moment :D.] Also, will Mirages have to align the INS properly or will allways aligned option be allowed ?

100% sure that it is MIL-STD-1553. People who worked on that confirmed that and iirc its some military version of a z80 processor which interfaces the MIL-STD1553 to the "old" system. Its somewhere in the 90000000 pages Viggen thread before it had its own subforum. EDIT: OCR'd manuals to the rescue:

MIL-STD-1553. Either it supports it, which it obviously does, or it doesnt. It can speak to the RBS15, which uses the same bus, quite elaborately. Setting a variable for ejection timing doesnt require an anymore computing power nor more bandwith then updating the weapons self coordinates, target coordinates or traveling altitude. I have programmed "computers" less powerfull then the upgraded Viggen ones. There is really no performance problem to implement such a feature. :D For the avionics, all it needs is the data panel to write a few flags to some register on the BK90s. Nothing it doesnt do with the RBS15. Could possibly also be set on the ground only. But given that the MIL-STD-1553 is used to set other values anyways. :) I mean I dont _know_ it, but knowing what is used for on the Viggen, from a technical standpoint it doesnt require a different functionality from the computer then what is already used by BK90 and RBS15. I dunno maybe there is another reason I dont know about, but thats why I am asking. :D

I dont know if I didnt notice in the manual, the manual has that feature not documented yet or the feature itself is still WIP. The timing between ejections on the BK90 should be variable. Probably it would be set in a similar way as the RBS15 seeker is programmed.

Gloorious. Looking forward to both events, much fun is to be had in both frames, in case flame decides to send me out ! ;D EDIT1: Would be nice if le mirages can have excess waypoints just randomly placed somewhere in the mission editor, ATM you cant use more waypoints then are defined by the mission editor, of the 20 waypoints the System is capable to handle. EDIT2: Did you mean that the mission itself will be published or that screenshots will be published ? If the mission will be published you can disregard this question, will the AWACS track, if there is one, be public ?

Run OCR then google translate, then merge alternating pages so you can have english and swedish next to each other in two page view. Works fine for me. :) There is pratically no english information except the ja37c manual. There was never a need for english info. So it doesnt exist pretty much. At least not in the quantity you are asking for. :) Asking the russian secret service for russian information is probably more likely to have relevant returns then anyone else for english. :D

Will there be mirage slots for ground attack, and how about viggen slots, since we will have it by then ? :D If Viggen gets released on 2.0 ofc... EDIT: Also will be composition of ground targets and position in 61B be known at takeoff, or is it more of a real deal you will have to adapt to whats there thingy ?

Mirage has similar autopilot features as well and i use it god damn 24/7 :D, seriously its one of the great mirage features: a capable autopilot. So It better is implemented, but honestly I expect nothing else then that from LNS ! :D

What makes you think that ? What does the viggen need, what isnt there ?