jackmckay

That means that DCS safe "Cobra" can only be done below 400km/h? - Question: At what fuel fraction and 2xR73 configuration Su27 have P/W ratio over 1?

Problem signature: Problem Event Name: APPCRASH Application Name: DCS.exe Application Version: 1.5.6.5199 Application Timestamp: 5915a631 Fault Module Name: lua.dll Fault Module Version: 0.0.0.0 Fault Module Timestamp: 584d6c6b Exception Code: c0000005 Exception Offset: 00000000000138a8 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1050 Additional Information 1: aa4e Additional Information 2: aa4e6e29e1b5aaff284a213e0ec6486e Additional Information 3: d095 Additional Information 4: d095242733e0c609963eab8156f2a96d

Dear ED. What is maximum safe IAS for FCS disengagement levels 1 and 2 without wing structural failures on max AoA. How Su27 wing accumulates structural damage and at what IAS and AoA? Thank you.

+1

Mister CrashO, I must remind you that DL is integral part of Flanker's avionics so removing that would mean removing RWR on F15 and Mirage. If you prefer that diskomfort acceptable for blue side I have nothing against removing DL feature on red side. Little story about DL hate: DL feature was removed from Fulcrum by ED crippling its navigation abilities without any explanation and on basis that DL feature was not part of standard Mig29 equipement even it has same device installed as on Flanker. So this story is over the edge of common sence since target data interhangeability is a feature introduced from Foxbat era. The only reason it wasnt on western export version is because export versions come stripped of from advanced on-the-grid features like DL and also they would need AWACS support. Who has russian AWACS brought today? -this story is not about ED misinterpretation of russian air-combat philosophy. Little story about 'denial of service by GCI': You have a GCI guy sitting on your blue slot. He has stupid name like 'hilly-billy joe likes USA' combined. Doesn't type mesages, doesent use SRS, is not on TS. Red have offensive and slip true grid of passive defences untouched. Someone on blue goes for cruical mission and flies in the mud out of radar scopes cutting the tree tops in between hills and walls from booth sides. Red group pinpoints the flight with precise accuracy 1 min after takeoff aiming at exact mission type flight neglecting blue CAP completely and blue SAM shield. 30 seconds after sucess guy disconnects. - and you say this is not what it is? Blue had numbers? - is that something new? Online streaming? -thats stupid. Last time we had a jokes on blue guy streaming his gradual deaths increased ratio. So you say that you havent recieved any intel from your GCI? -thumbs up for great sucess but none can speak for the whole team. Principle of mole: Register another user on ED. Buy CS for 10bucks. Run DCS on VM on another monitor. Enter oposide side GCI slot. Stream F10 map for SA unaware users to become 'better pilots'. Pest removal options: A) Dismiss GCI slots completely. B) Fog of war? C) GCI needs aproval from other players in-game (min 3 players egg.). D) GCI needs to register for GCI role on BS forum.

We had a blue guy (with badly chosen nick) sitting on a red side GCI slot last night using slot as position intel. That's why last night blue side got up to Gudauta and they knew exact intel. At the end of blue mission this guy just disconnected. I suppose this guy has multiple profiles and registering one on blue and other on red. Knowing that (this guy) and geting along with that (the whole team) is playing the least in a manner of fair-play game and its sucess is not valid sucess of any kind. Dear Ciribob, either setup 'aproval scenario' for GCI slots or ban them completly. I vote for GCI ban.

We need to turn off the GCI slots because of spies. Total darkness for all!

Great job man. :thumbup: Tell me how did you set model acceleration performance. It looks like to linear up to sudden stop on max speed. Is there some blending of speed versus drag charts?

Roll back drivers.. nooo.

Again.. Problem signature: Problem Event Name: APPCRASH Application Name: DCS.exe Application Version: 1.5.6.5199 Application Timestamp: 5915a631 Fault Module Name: lua.dll Fault Module Version: 0.0.0.0 Fault Module Timestamp: 584d6c6b Exception Code: c0000005 Exception Offset: 00000000000138a8 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1050 Additional Information 1: aa4e Additional Information 2: aa4e6e29e1b5aaff284a213e0ec6486e Additional Information 3: d095 Additional Information 4: d095242733e0c609963eab8156f2a96d

BF could at least offer some role slots for these two mighty planes. I think they deserve that place.

TacView analysis could find lag occurances if output data stream has better resolution since TV has kind of datablending or smoothing. That could be a good method without extra load on processes. Heinsenberg uncertanty principle? Too much of quantum physics. Lag is recognised by DCS gamer's eye as sudden and large displacement of ingame object, not a matter of high resolution measurement and analysis of bject momentum in realtime so by introducing treshold limits or out of trend object predicted behaviour we still can detect lag occurances by simple export data analysis done on game stream extraced data.

We don't have LAG statistics and we just know that is present now. We should see who is lagging, what type of unit, where and why. Lag detection script could solve that part and give a good tool to gamemasters. Just calculate occurrences of rapid displacement. Simple as that :)

Red needs some fine mig21 pilots and good GCI and we kick lot of blue asses - eventually. In the meantime - choppers wars.

I think that radar on 27 is buggy. I see target visually but needs like 10 sec of HI/MED/ILV*Range+/-50km*Elevation+/-5km before acquiring target. Locked but if mode changed and returned to previous state needs next 5-10 sec to acquiring again. On SP it works much better and faster. Being merged gives better suitability. PS. Do we have some 104th guys here on BF after yesterday's Red victory?

1) DL is gone today. Why? 2) Could someone write a 'lag detection script' so one who lags too often gets statistically warned, on repeat kicked or even banned? 3) Maykop Su27 slot 20 was broken yesterday.

Based by my observation definitely more than radar gimbals limit of +/- 60deg. What I stroke here is that in combination of unrealistic m2K radar locking capabilities, 530D is behaving like ARH missile instead of SARH BF rule. Can anyone confirm this case?

Can anyone confirm that mirage radar keeps tracking lock in off-boresight angle for 530D?

Too much countermeasures(m2k) on countermeasure hungry missiles(r27s). Mirage's 530D was introduced later than 1983 time stop in 1988 so its over the time limit. Mirage is also fast so it can outran and outdecoy R77 and its radar has anomaly of locking targets thru pilot butt so this usage is justified until Mirage is fixed properly. ETs on the other hand would hit too much blue without knowing that they are attacked. R77 would give them a chance to evade.

Even they are two Matras they are very effective (PO some would say) but Es could be fired from longer distance and they are very countermeasures hungry so still there's advantage to the mirage also they booth can carry two LR missiles. Anyway I would put something more effective under Mig29S to counter blue exclusive Mirage scenario. Agree? PS: But when looking at countermeasures ratio R77 is right balance tool for M2K vs Mig29 combat as mirage can carry more countermeasures (32flares/130chaffs vs 30flares/30chaffs). I vote for R77 in this case.

How about Gen4 fighters with minimum 5mins of full afterburner time ramp ready (gen3 interceptors fuel max as before)? That means same minimum flight time available without fuel loading on ramp because different planes have different consumption rates so this would be even for booth. 1980-ish time lock is fine by me and core of BF scenario. And what I would really like to see is strict Cold War East vs West airframes and same gen plane numbers equal on both sides. Meaning Mirage strictly blue but equal numbers of mig29s (with either ETs/ERs of R77) on red, no A10s and Hueys on red and no Mi8 and su25T on blue. That means no visual recognition mistakes and less IFF errors. Eagle numbers qual to Flanker numbers, Mirages equal to Fulcrums, Tigers equal to Fishbeds, Warthogs equal to Frogfoots Su25Ts, Viggen equal to Su25s or another set of different skinned Fishbeds, Gazelles equal to black Sharks, Hueys equal to Mighty 8s etc. Recon flights with few defense-able Sabres vs Mig15s, Transport booth with TF51s and I think everybody would be cool with that. No technology handicaps except missile production time set to 1982-83 restriction prior to 120s(1982) (https://en.wikipedia.org/wiki/AIM-120_AMRAAM). Since Matra 53D is introduced in 1988 this balancing would be done by alowing R77(1982) on Mig29 or even ETs or ERs for compensating efectiveness and range of Matras. Next, by my personal obsevation, bomber calls are to effective even with reduced numbers of bombs droped so I sugest using Sabres and Mig15s that would need to land on nearest friendly airport to deliver captured intel. If on same airport as bomber start point one could see bomber on ramp taking of for its run and even folow it with egg. mig21 or F5. Bomb number should actually be full bomber capability but this way bomb run should be a little trickier because recon flight would become target of interest upon return to friendly base as man hunt would start at that point. Next, airfields have to weak defences and should have inner rings of defences like more IR sams and AAAs. But again West vs East side types egg. Vulcan vs Shilka, BUK vs Thor etc.. Its too easy to deplete LR SAM missiles because they shoot on anything. Also ground eclosed AA guns would be cool to. EWR system is looking good for DL and I hope for all GCIs. :pilotfly:

Where have all bluefor players gone?

Still crashing: Problem signature: Problem Event Name: APPCRASH Application Name: DCS.exe Application Version: 1.5.6.5199 Application Timestamp: 5915a631 Fault Module Name: lua.dll Fault Module Version: 0.0.0.0 Fault Module Timestamp: 584d6c6b Exception Code: c0000005 Exception Offset: 00000000000138a8 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1050 Additional Information 1: aa4e Additional Information 2: aa4e6e29e1b5aaff284a213e0ec6486e Additional Information 3: d095 Additional Information 4: d095242733e0c609963eab8156f2a96d

'target rich environment' :D +1 Bluefor don't use logistic feedback. Everybody wants to hunt for targets and few use choppers to drop stuff around. This server is all about teamwork and Redfor does it better. Red conquered area from Sochi to Senaki in 1 day. Great sync and fast role switching - key to success. Redfor rules this test round. :thumbup: @Ciribob: I noticed that Redfor has 5 Mig29S slots (1 at Anapa and 4 at Krymsk) so that should be at least like 4+4 and little closer to the central area of conflict zone. Mig21 is 3.rd gen fighter that should fight F5s not M2Ks on frontline so half should be replaced by Mig29s.

TrackIR is allways on so I didn't try that. Will do. Just updated TrackIR software to 2016 version and going for testing... It looks like the cause of this was outdated TrackIR driver software. It doesn't crash for now.