Jump to content

Corsac

Members
  • Posts

    40
  • Joined

  • Last visited

Everything posted by Corsac

  1. Easy comm's aren't enabled. I do use a mod: but I don't think it's really related. Totally unrelated to this though. Please check the CJS SH Discord pins.
  2. Thanks for the info. I'm not sure if the original mods author still read this forum but my request was to their intention. I can point my server admins to the hotfix but I guess they're unlikely to apply it since that would means all clients would then still need to apply it as well, and it's unlikely to happen unless there's a release to be made...
  3. Here's an example of a non working situation. The SRS window indicates COM2 is receiving, but in the cockpit it only shows M and not ^ null
  4. Thanks for the link. It'd be nice if that fix could be integrated in the source and a new release be made? I've made the change myself and it seems to fix loading the SuperBug but then apparently on other servers (like Grayflag) using the Anubis mod, the C130 is replaced by the Su-27 image (which I think is usually the sign of "you don't have the mod correctly installed")
  5. I think maybe since last update, there's no indicator on both radio when they're receiving (through SRS), only when they're emitting. Is that correct? Actually scratch that, it works at least some times
  6. Hey, I just wanted to report that the Hercules mods seems to conflict with the recently released 2.4 version of the CJS SuperHornet mod ( but 2.4 installs in Saved Games). The dcs.log output here shows: 2024-11-29 23:57:11.764 ERROR LuaGUI (Main): [string "Scripts/Database/db_main.lua"]:37: bad argument #5 to 'format' (number expected, got table) when running a SuperHornet mission with the C130 mod installed. Error disappears when the C130 mod is moved away. Apparently it could be because the C130 mod access warehouse data in a way incompatible with recent DCS versions. I know there's no work done on the mod for now but maybe a simple patch would be possible (i'll try to investigate and report back) So for now it's likely you have to chose between the Hercules and the Rhino.
  7. Also it seems that even if you're lucky on the first slot selection, changing slot during a session will always end up blocked.
  8. So I just tried a sortie on Grayflag Sinai with JDAM and they were all duds, very frustrating. Not sure if you still need a track (I might have one but it's the whole sortie and it's 55MB, tell me if it's needed). I took 4× GBU31v3 (penetrators). I've configured them with: FMU-143 fuze (from Wags video I understand that's the "penetrator" one), I left the arming delay to 5.5 (default) and set the fuze delay to 0.12 (for penetration). I've dropped four of them on bunkers, two missed completely (a bit unsure why) but the two that hit seemed complete duds. The current situation with fuzes is really frustrating. Everything seem to be buggy and it's pretty random whether your sortie will be successful or not. I think some of the problems are "skill issues" but it'd be really helpful to actually know what DCS expects as fuzes for different weapons and different effects. We can try real world documentation but we have no idea how it's implemented in DCS so it's be best to have DCS documentation. Thanks for any help on this and again if you need the 55M track just ask.
  9. But thanks to the Alt-Enter pointer, I've investigated a bit and switched my setting to Fullscreen. Now I can Alt-Tab and back after a disconnect/connect and it seems to work. So maybe I do have a workaround for now.
  10. Hey, thanks for the feedback. I've tried the two solutions (mouse clicking the desktop and Alt-Enter) and none of them worked, unfortunately.
  11. I'm using a multi-monitor setup as well to export MFCD. It works fine but when the second monitor disconnects (because I switch it to a different input), DCS will compress the whole screen on the first monitor instead of just dropping the second viewport. And when the second monitor gets back, it doesn't expand back the image. Is there a way to force DCS to redetect the monitors?
  12. Hi people [sorry it's a duplicate but I don't think I can move topics] I don't have a trackfile and I'm not sure how to reproduce, but I experienced a weird problem yesterday. I was flying on the Sinai Grayflag server, carrying GBU12 bombs and ATFLIR to do the targetting. I drop all but two GBU12. Everything went just fine but at some point I had to refuel. I landed on an airbase (St Catherine), asked to refuel/rearm. The base ressources were empty so I didn't load any new weapons. Then I took off and went to the operation area, but when I tried to select the GBU12 (82LG on the SMS page), nothing happened. Actually I could see it did something because "step" appeared on the DDI, but I couldnt do anything more (EFUZ, CODE etc.) Attached is the DDI screenshot. null Unsure if it's related but at some point in the same flight, my AG radar display in GMT mode was diagonally crossed (the cross was slowly blinking). know it'd be more helpful with a trackfile but if someone experienced the same issue I'd be interested. null
  13. Hi people, I don't have a trackfile and I'm not sure how to reproduce, but I experienced a weird problem yesterday. I was flying on the Sinai Grayflag server, carrying GBU12 bombs and ATFLIR to do the targetting. I drop all but two GBU12. Everything went just fine but at some point I had to refuel. I landed on an airbase (St Catherine), asked to refuel/rearm. The base ressources were empty so I didn't load any new weapons. Then I took off and went to the operation area, but when I tried to select the GBU12 (82LG on the SMS page), nothing happened. Actually I could see it did something because "step" appeared on the DDI, but I couldnt do anything more (EFUZ, CODE etc.) Attached is the DDI screenshot. Unsure if it's related but at some point in the same flight, my AG radar display in GMT mode was diagonally crossed (the cross was slowly blinking).null nullI know it'd be more helpful with a trackfile but if someone experienced the same issue I'd be interested.
  14. Hi, it seems that right now it's not possible to use the radio mode of the voice chat feature while using a JTAC/GCI slot (in CombinedArms). Ctrl+Shift+Tab shows the window in room mode, but you can't access the radio mode. In the voice chat settings, there's no unit for JTAC/GCI so no way to even "add" a custom radio or something. So you can't actually talk to the pilots in the air.
  15. It seems that there are multiple requests about this: and There are also multiple cold war oriented servers which fueled interest in less moderns setups (for example Enigma Cold War and Tempest Blue Flash). Even if it's not the only issue with the Hornet and Viper versions we have in DCS (which are pretty modern), having a way to restrict Link16 and JHMCS would really help balancing those missions. As a first step, being able to detect this usage in mission scripts in LUA would help: maybe have them appear in getAmmo() or getSensors()?
×
×
  • Create New...