pchRage

Attached miz and track. Lock target in FCR and STT mode notice 4 bars switch to ACM mode Bars now set to 1 go back to Nav Mode, radar stuck at 1 bar move to MRM mode radar stuck at 1 bar unlock target, radar stuck at 1 bar go to MRM mode, radar stuck at 1 bar etc etc Must manually use OSB button to reset Bars TestACMBars.miz LastMissionTrack.trknull

Is there any update on a fix? All the threads on it are locked and its been months. Yet again had a 3-ship flight with HTS and STNs setup on public server. Was able to TDOA ~3 seperate SAMs before my HTS bricked with the int.min values. Then swapped TDMaster over to my #2 wingman to start TDOAing and sending markpoints. They were able to send ~4 marks before theirs bricked. Then had #3 wingman start TDOAing. Cycling pod on/off has no affect. We did see that while its bricked, it can still participate in the TDOA and send data (can see lines draw), your just 100% unable to move the cursor. Had to switch to WPN/HAS to fire the remaining HARMs to salvage the sortie. Server track file too large and not Caucuses.

Similar ask, having yaw effect from center is something I think would be amazing for prop plane where coordinated flight is a constant battle.

Thanks. When i have time ill try setting up a sp msn where i can use a radio cmd to deactivate the sam while tdoaing and see if i can get a repro

nullThis was an odd one, sorry I do not have a track, was in MP, Sinai... 4-ship flowing towards target area. a SnowDrift popped up on HAD. I TMS UP'd it, got a lock, and then proceeded to TMS Left long to send TDOA. The wingman lines started to connect to the locked emitter, and then the SD dropped off the HTS/HAD (ie it went dark, etc). Kaboom! My HAD bricked. the cursor disappeared, and there was that -2 billion values for the cursor-to-bullseye value (red circled in screenshot). I tried TMS down, I tried changing THREAT classes, EOM/PB/etc modes. I tried locking a target in TGP , FCR... I tried cycling to NAV, A2A, nothing worked. I even powered off the HTS hardpoint, turned it back on, waiting till it spun back up.. and it was still bricked.

Sorry do not have a track, perhaps someone can provide. Join flight of 4 Set HSD to coupled mode Set Radar to SOI Hold FOV to auto zoom HSD scale to show all flight members DCS crashes

Thanks for the reply! And at altitude its flipped the other way (RMax 38 > 31) because of the time gravity can affect the extra weight or ?

Any idea why on the deck, > 1.0M that the GBU-38 top of the staple RMax is ~4.2nm while the 31 (and 31v3) are around 6nm? Maybe the guidance kit/fins are larger on the biggie and can semi-glider further? Feels backwards given the 500 vs 2000lb sizes... And when your at, say 28k AGL > 1.0M, you can typically hit RMax around 17nm for the -38 vs around 13nm for the -31....

thank you for the replies. sounds like I misremembered the stall horn! Just finished reading that long overheat thread... almost sounds like I can stop doing the "hold oil cooler open" dance!

Haven't been in the 51 in years, last time I flew it for any length of time was when the new DM / xray system came out.... Anyways... saw a couple things and was hoping all you dedicated pony drivers could clarify. Engine temp mgmt. I believe a read that it got an overhaul after the p47 modelling was complete. Seems to overheat just as easily, but it cools down a tad faster than before when holding the oil door open... havent bricked an engine so seems better (havent tried auto-death WEP yet though) Xray DM. Such new cool fx, especially to pilot injury! I remember the only way to take down a 109/190 was to saw off a wing, anything centerline would just absorb the hits. Could NOT shoot off a wing no matter how many rounds/convergence/etc. Even the 51 seemed to take enormous damage and still limp around Stall horn. Maybe I am misremembering... but I get zero stall light/horn. Shake/buffet is only sign before the dreaded left wing stall. When using the rear RWR, it alerts just fine. Is there a switch or something new required for the stall horn? I tried both left wing stalls, as well as just idle and climb wings-level to stall... nothing! AOA at 20deg seems to auto-induce left wing stall, regardless of speed or horiz/vertical plane of motion... hit what appears to be a magic 20deg and snap! Ammo belts. The '44 Strafing seems the ideal choice with API and API-T... but honestly.. i didnt see anything special when hitting.. maybe a hit caused a fuel leak, maybe i saw dark smoke (oil).. but the "I" in API didnt seem to do anything... Sad Face: pilot green jumper / no convergence settings Any insight appreciated!

Thanks for the feedback. My goal is firing with zero search/track radar. I may try the HQ7 with its optical mode next..but not too hopeful...

Hello mission builders! I am trying to have a scenario where SAMs are fired ballistically "for effect/immersion"...not to actually hit an aircraft... based on a trigger ..not utilizing a track radar lock... I tried the "fire at point" with no success. About the only thing I can find to "work" is the SCUD.. but it doesnt have enough smoke trail for the effect I'm looking for. Any ideas? Thanks!

thx. will try it out and see whats what next time

yes we've run into that PG nighttime DL bug... this was ~0600 Syria 2018. Also, BlueFOR did have AWACS and DL was working just fine...it was only REDFOR without awacs that had the issues yes yes missing track file.. per original post I have it, but its 60mb...

thanks. INS was good, RF and Mids all on and the 4ship had no issues with alignment, comms, yardstick, etc etc. We were using green comms encrypted on victor... maybe that interfered? Checked the mission and unrestricted was "not on". but this was 2018... doesn't that value only deal with pre 1994? and we were all at alt, in same general 40nm kill box... couldnt see each other, couldnt see when someone else locked a bandit, couldnt see when someone would stt and then DL send bandit... nada