Jump to content

pchRage

Members
  • Posts

    192
  • Joined

  • Last visited

Everything posted by pchRage

  1. 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
  2. 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.
  3. 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
  4. 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 ?
  5. 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....
  6. 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!
  7. 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!
  8. 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...
  9. 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!
  10. 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...
  11. 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
  12. Multiplayer mission as Redfor on Syria circa 2018 ~0600. No AWACS in mission, but was expecting F2F DL. No amount of mucking with switches showed our 4-ship to any of us at any time. Even attempted sending a DL air contact... would give alert to wingman/element, but nothing appear on HSD for them either. IFF Left short/Long would show brief green circle on FCR for targets..so that was working, just no persistent F2F...even cycling IFF L/R All/None and All/Fght/TGT didnt change anything Have track, but its MP and ~60mb so probably not helpful.
  13. Thanks for helping clear up my explanation! Attached is a test miz and track file. Track demonstrates repeated zooms and having to reset CPL mode after each time. Whereas the regular quick press zoom to EXP1, 2, Norm on HSD does keep it in original CPL or DCPL mode as expected..its only the Flight zoom that "breaks" so to speak. HSDZoom.trk TestZoom.miz
  14. Realized this was occurring during a 2+ hour MP flight... so no track... wondering if this is supposed to happen? 3-ship flight..ie 2 DL wingmen set HSD to Coupled mode long hold on Expand button makes the HSD zoom in/out to show the whole flight (awesome!!!) release Expand button and HSD go back to original zoom level...BUT HSD is now in Decoupled mode! I'd think that on return/release from flight zoom mode, the HSD mode (ie Coupled) would be maintained..
  15. Is there an ability to set the jetpad to react to YAW? I'd like to have a setting (think WW2 birds) where the further away the rudder/yaw ball gets from the center the greater the feedback in the seat on that side.. so you can tell just by feel that you are out of trim/diving and to apply rudder till it stops. And something like the G-feeling slider on the Special Options tab where you can set a deadzone min/max for yaw.
  16. Could be. If I make the left MFD the GM/GMT radar (or any other page) it doesn't cause the same TGP snap/swivel though... only the HAD page
  17. SP test mission with 1 STP at a large tech-combine building and an EWR offset ~10nm to the west. setup left MFD as HAD and right MFD and TGP select GBU-12 as weapon set GBU-12 to CCRP mode make HAD SPI and TMS UP on EWR. Note TGP has swiveled over to EWR general location make TGP SPI Note TGP has NOT moved from EWR general location TMS down to reset TGP Note TGP has swiveled over to STP 1 TMS Up on TGP to set a point track on the building Note point track box, countdown timer for GBU, etc etc Now.... make HAD the SPI (do not touch TMS) Note the TGP has now dropped its point track and swiveled back to EWR I think because the HAD is still "locked" on the EWR.. it forces the TGP there without any input and you lose the point track If you make the TGP SPI again, nothing happens.. it doesnt go back to STP nor to your previous point track... you must TMS down to get it back to STP 1 and then re-point track. Is this as designed? TEST-HTS-TGP-SPI.miz HTSTGP.trk
  18. i agree! but its worked consistently in 2d air/hot start, and never in vr (hot or cold), whether SP, Enigma server, private server, etc etc
  19. Great to know! That could explain my cold start 2D test..Ie i didn't wait long enough... I will say I have never gotten tacan to work in VR in the F5. the distance is always the barber pole blocked off. even with air start...
  20. Figure I should just add to this thread. I created this simple mission with ground start with LOS from Vaziani to Tbilisi (25X). When I setup the mission for ground start HOT, the tacan works just fine. When I set it up for ground start cold, and do the startup routine.. tacan never works. I tested both scenarios in 2D and VR... TACAN_F5E.miz F5-Tacan-Cold-Fails.trk F5-Tacan-Hot-Worked.trk
  21. well this thread went sideways Thanks for the feedback though! Given USAF "always?" runs wing-tanks, sounds like there is zero application for the 4x JSOW loadout. Having to use gate just to transit to the AO... and also assuming launch would be >=30k for optimal launch range it would be even further impacted.
  22. Simple SP test mission. Caucasus default setup... no wind, 25k AGL, S to N flow to a STP ~60nm away. Full mil starting at 0.8M. Set auto-pilot for alt/course and observe.. Same load-outs for F-16 and F-18.... F-16: 2x120, 2x9x, 4xJSOW-A, 2xtanks, tpod, no pylon center, no hts F-18: 2x120, 2x9x, 4xJSOW-A, 2xtanks, tpod on center F-16 continually loses speed and increases alpha till its at a paltry 0.67M at the stp. F-18 accelerates to~0.93M by mid-distance and maintains to the stp. I know its sort of apples to oranges, but I wouldn't expect the F-16 to fall out of the sky. I basically must use at least min AB to maintain speed... The only way to get close to the same speed as the -18 is with only 4xJSOW, no missiles, zero pylons...completely clean.. and even then.. its 0.90M not .93... In order to not fall out of the sky, I can swap the wing tanks for a center tank and leave everything else as originally tested... that will at best hold 0.80M... Maybe this is completely accurate and you just cannot combine double load jsows with wing tanks... testJS.miz
  23. Any comment on this? It's pretty challenging for F16s against other modules already...but when you finally get to a perch with the T/W E game, its very hard to cash it in due to having to eyeball the shot with just the gun cross and funnel as radar is out-to-lunch.
  24. Thanks for the feedback, what you are saying does describe what appears to be happening. So.... does ED consider this ACM behavior a Bug or Correct-As-Is ?
×
×
  • Create New...