Jump to content

Fulcrumkiller31

Members
  • Posts

    114
  • Joined

  • Last visited

Everything posted by Fulcrumkiller31

  1. Bumping this thread to keep it alive. It happened to me today about 3-4 times an hour, yesterday it was fine. Still zero clue what could be causing this. Winwing is sending me a cable but I have little hope it will fix it.
  2. I think the missile is performing really well, besides the random pull-ups that happen. AI is just too all knowing and too perfect.
  3. It’s pretty hard to notch a Phoenix in DCS at least the C. It’s coming down at such a steep angle. I also get low and look up at the target in the last 30 miles. Also, In the words of my father, a former tomcat pilot “it’s impossible to notch a Phoenix” may or may not be true but isn’t it a MPRF missile ? If they do split S, I chase them down and follow up with sparrow or Phoenix shot to the face (motor burns the whole way if they turn back into me.
  4. I personally appreciate the transparency when modules are announced. I think we all know these things take a lot of time. More information on progress is appreciated however. More modules and maps are always a good thing regardless if they are things you are interested in. Not a single other game exists out there that can compare to DCS. It’s only going to get better ! Especially with multicore !!!! I remember the days when Black shark and the A10 were the only modules to exist. I was so hyped when the MIG21 was announced, so who knows what the future holds .
  5. I haven’t had any issues like that, I’ll typically launch high 30s or low 40s close to m1 . TWS launch on fighter around 55-60nm . Pretty much guaranteed hit as long as they don’t split S . STT will launch 65-70 and same results.
  6. I really hope there is an easy fix somewhere . I am about a week away from exceeding my 1 year warranty… still having completely random disconnects. Somtimes it’s once a night . Others it’s 15
  7. Yup... tried, seated as far as it could go. disconnected twice in 20 mins. No clue what could cause this.
  8. It is as far in as it goes... will reseat and try again
  9. Well it happened a few times in a row the other day, I retightened the connector in the base and it seemed to help as it didn’t happen again for the rest of the evening. I am at a loss if the powered USB helps , or just masks a problem with a loose connector/ poor design / poor quality connection (stick to base connection) I have zero solid answers , really sucks when you are bombing a target the stick disconnects and you spiral into the ground after an hour of prep.
  10. I ran a repair and it worked! Well sorta, the drop cue didn't march down but I held down weapon release and when it hit zero the bomb came off normal. Misunderstood the symbology I was expected to receive. Unless it still is not quite right. GBU126works.trk
  11. Forgive me if this is normal, I find it a bit odd, no release above above a certain alt. At first I thought it was 24k, however that proved to be incorrect as the bomb dropped around 27k. Anything above 30 and I would not get any release symbology beside the toss anticipation. Is this a bug, limitation, or user error? GBU12.trk GBU122.trk GBU123.trk More tracks GBU124.trk GBU125.trk GBU126.trk
  12. Great to hear ! Thank you for the response
  13. FYSA this has been recreated both above 15k and below 15k, auto lase and manual lasing through the whole time. Bombs will fall short regardless, fail to capture laser, or capture but fail to pull back up and hit. If released near the bottom half of the DLZ the bomb has a chance to hit. I implore yall to test this for yourself!
  14. I tried it with the hornet and it does the same thing, except the DLZ is much smaller. so it captures the laser.
  15. Really odd ED would do that. Does this also apply to changing the Fusing of weapons?
  16. Yeah same thing on my end. The bomb just takes a nose dive. GBU24 odd behavior2.trk
  17. Lol it is certainly odd, wish I didn’t get the immediate cannot reproduce tag. something is clearly off.
  18. From my understanding of bombs like the GBU 12/10/16/24 , the laser code is changed on the ground. is a irl feature of the F18 to be able to do this on the fly ? Until recently I believed it was real, but upon further research it appears to be a made up thing in DCS? just looking for clarification from ED on this
  19. "However, if the LGB guidance system detects reflected laser energy from the target designator too soon after release, it tends to pull the LGW down below its required trajectory and the bomb will impact well short of the target." I think it totally depends on launch parameters when you should lase. good read indeed. Check out my above track.
  20. Upon further testing. The issue seems to lie with the bombs not seeing the laser when dropped from max DLZ above 15000 ft. With a 10 degree loft- bombs capture laser wait a bit to around 10-12 miles bombs capture laser. 24k ft level drop from around 14 miles M 1.2, bombs don't see the laser until they are ballistically too low to make the target (although they try). Below 15k feet, I have a few successful hits, bombs glide like they are suppose to, but sometimes one of the two bombs never catches the laser. Some SME feedback on discord confirms this, these bombs are pretty complicated, there is a lot more to it than dropping in the DLZ. Although I still feel like there might be some wrong behavior. GBU24 odd behavior.trk
  21. I can’t find any documentation stating the GBU 24 needs laser energy immediately. In fact I read the opposite. either way it still doesn’t work !
  22. Still fell well short. Tried again and waited until I was halfway through the DLZ, it barely had enough energy to hit the target. GBU24 borked2.trk
×
×
  • Create New...