Jump to content

Kondor77

Members
  • Posts

    26
  • Joined

  • Last visited

About Kondor77

  • Birthday 07/27/1985

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. For #1 (I assume), at a minimum we (who own the SC) should be able to place the SC statics on the Forestall. Currently we can place them on the Stennis and on ground AFs. So we'll at least have people/cranes on the deck. They won't be moving or doing anything like they would on the SC though. Hopefully this will serve as a good interim solution until it gets developed further. As for #4, I assume if it's done as a Stennis clone that since it probably uses the same framework, that the AI should have no issues with it?
  2. On your last point about AI omniscience, that was actually fixed last patch. They now no longer evade/chaff until the missile actually goes active (I'm speaking strictly about TWS shots). I'm consistently making hits on AI fighters at 50+nm when firing in TWS.
  3. Interesting, it is the same account and I can play the campaign in SP. Maybe it takes some time for it to update server-side? Gracias por la respuesta
  4. Hi all, I'm trying to load these missions into my server box in order to help with FPS (I don't want to reduce the # of planes using F10 menu - and the server box helps a ton in this regard). But when trying to load the missions I get this error in the dcs log file. 2021-05-21 16:41:37.095 INFO WORLDGENERAL: loading mission from: "C:\Users\jmoli\Saved Games\DCS.openbeta_server\Missions\P-47 Wolfpack\Wolfpack - 01.miz" 2021-05-21 16:41:37.739 INFO DCS: use_xRay: yes 2021-05-21 16:41:37.739 INFO DCS: netfm_enable_coeff_switching: yes 2021-05-21 16:41:37.833 ERROR Dispatcher: Mission Load Error: Mission is not authorized. I get the same error even trying to load even one of the 'Coop' missions: 2021-05-21 16:41:43.208 INFO Dispatcher: loadMission C:\Users\jmoli\Saved Games\DCS.openbeta_server\Missions\P-47 Wolfpack\Wolfpack - 09_COOP.miz 2021-05-21 16:41:43.208 INFO WORLDGENERAL: loading mission from: "C:\Users\jmoli\Saved Games\DCS.openbeta_server\Missions\P-47 Wolfpack\Wolfpack - 09_COOP.miz" 2021-05-21 16:41:43.989 INFO DCS: use_xRay: yes 2021-05-21 16:41:43.989 INFO DCS: netfm_enable_coeff_switching: yes 2021-05-21 16:41:44.075 ERROR Dispatcher: Mission Load Error: Mission is not authorized. Thanks in advance!
  5. For the time being, a way around this in MP is to input the coordinates for the waypoints manually using the Jester wheel. It's obviously not as quick or easy as F10 markers - but it works.
  6. I posted about this in the bug subforum and attached my log file. I tested it in SP and it works, but as soon as you try it in MP it CTDs. Manually entering waypoints with Jester wheel works in both SP and MP.
  7. As the title suggests, game hard CTDs when using the Jester option to add a waypoint from F10 map. As for my tests, this only occurs in MP. dcs.log dcs.20210414-183148.dmp dcs.20210414-183148.crash
  8. Thanks, there are other tracks as well posted here:
  9. I can confirm I ran into this bug as well yesterday. I'll see if I can upload my .trk file. This actually is one of the Reforger 'Iron Heel' campaign missions from HB, running off my dedicated server with me and my human RIO as the only clients using the SC. I got the same 'Flight is delayed' message, spawned in soon afterwards and immediately noticed the plane felt like it was stuck in mud, needing way more throttle than normal to taxi. Cat launch and trapping all exhibited the same effects of having this ghost weight onboard. **EDIT**: Track file download link: https://drive.google.com/file/d/1nrG3hSZvyx19XATlYGXUd1-ZX0wNQykJ/view?usp=sharing
  10. It absolutely has to do with head position at launch, which is a really cool touch.
  11. Looks like sparrows also got borked in the update. I'm having the same issues posted here - with all sparrow variants. AIM-7MH Issues - Bugs and Problems - ED Forums (eagle.ru)
  12. Thank you for the update Cobra. When it comes to the 'General Jester TWS-A issues specifically to desync/track loss issues, I'm not sure if others have mentioned elsewhere, but I think I've found the culprit. It's the Datalink. I've only had enough free time to test it myself about half a dozen times offline and online. If I make sure my Datalink is set to anything that's NOT the AWACs, It eliminates the issues with the desync/ghost contact which lead to track loss. Hope this helps, and can't wait to wrestle with the A.
  13. How are you inputting waypoints? If you're doing it through the F10 map then Jester, he's kind of incapable of doing multiple waypoints at one time, and I've had this issue happen if I stack more than one waypoint at him (from F10) before he's done the first. You can follow in your TID repeater, so when he's done the first waypoint, go through the Jester menu again and add waypoint 2, and so on.
  14. I tried it a week ago and it worked. Now, I'm doing this without the LANTIRN pod and with Jester. The behavior you're describing sounds like you're too high in altitude. It really works best at the mid/high teens. Around low 20s it becomes very hard to designate a point on the ground, with any time left to line up a bomb run.
×
×
  • Create New...