Jump to content

BLUEmako

Members
  • Posts

    46
  • Joined

  • Last visited

Everything posted by BLUEmako

  1. Can also confirm disabling super carrier fixed the spawn screen hang. Lag only seconds now instead of minutes.
  2. That is an incredibly short-sighted position from enigma. Literally the only recent move to lower the barrier of entry to these cold war classics should be jumped at. Enigma himself posted a video arguing that lower fidelity was the way to go, silly to not support this for the sake of some spawn point edits... Heatblur please add these fc variants. Given the relative unpopularity of the sabre and MiG 15 you would only need to convert some of the full fidelity slots to the FC version and then those with fc4 can give these aircraft a go in mp.
  3. I'm trying to join ECW but the select screen hangs. I get the greyed out "program not responding" effect. I noticed DCS is using up about 35GB of my 64GB of RAM while trying to join ECW. I have disabled my add on mods but still get a hang in the select role screen. Takes about 10 minutes to register a mouse click. I noticed after about 20 minutes it loaded in and displayed every single spawn point in the map. This behaviour is just ludicrous.
  4. Are the FC versions of the F5, F86 and MiG15 going to be available on ECW? I have tried to join to check but the current issues with the role select screen mean I can't do anything once I join...
  5. Same issue here. "English" setting in special doesn't change the cockpit at all.
  6. Same issue here Long time FC3 owner, authorization failed, attempted reinstall, loops the failed authorization message and FC3 greyed out in game. F5E module is fine for me.
  7. I am currently struggling to wonder how Jester 2.0 has kept his seat as WSO in the Phantom. Don't get me wrong, I love flying the F4, however I'm finding it very frustrating whenever I need to rely on Jester. Jester is family, I don't want to speak badly about him, we've spent a lot of time together in the Tomcat, but I feel like he should have been held back in school a bit more to just get the hang of things better. Some of the frustrations: - Jester menu opens but then I can't select anything for several seconds as the radial selector doesn't come up immediately. Even the simplest command becomes way too slow for combat. - Jester simply cannot use the radar effectively. I have not been able to get him to lock onto anything for BVR before I am in visual range and in the merge. I may as well not carry sparrows and leave the radar off. This is true even when I can see the bandit I want him to lock. - Jester is so slow calling targets in a dogfight they are long gone from the direction he indicates when he makes the call - When he calls contacts he doesn't give the complete call, he usually says something like "5 miles, 10 degrees" but doesn't indicate friendly, hostile, type, altitude. I'm left guessing what it is he has forgotten to tell me. - Jester hates the IFF and refuses to touch it when I ask. I can't shoot at anything until I have visually ID'd it. - In multiplayer I may as well not have a WSO at all, he's so slow and can't be trusted to call out threats. Hopefully these frustrations can get ironed out pretty fast and Jester and I can be friends again. The relationship is pretty strained right now.
  8. This happened to me on ECW server
  9. No I wasn't aware I needed to use the context button for this. I used the jester radial menu to ask him to change radar. However I'm guessing jester shouldn't say affirmative and then do nothing
  10. I've found that when I am dogfighting and use cage for BST mode that once the dogfight is done and I want to get Jester to search he will not set the radar back to search and long range. He will respond to the UI command to set 50 or 25 mile range but does not change any settings. Radar stays in 5 mile range unless I use the mode switch to B to reset. Manual says WSO should be able to do this by hitting A-A in the back seat?
  11. I saw a thread for this in A10C bugs but this is happening in A10A for me. High frequency shaking of jet in flight. Can't seem to isolate to speed or aircraft settings. Started with latest patch. Checked and not related to my setup as does not occur with other modules I have.
  12. Also have George controls in middle of screen. Is there a way to set location in the monitor lua like the jester menu for F14?
  13. First to IronMike & HB thanks for the transparency with this thread, it's appreciated. Few questions though: 1. Did the changes to the phoenix performance include changes to the parameters for launch cues in TWS mode? I ask because since the changes I cannot get hits using the flashing TWS track cues as a guide to launch. The phoenixes run out of energy well before reaching the target and/or fail to guide in the terminal phase. 2. I've seen several phoenix just loft for outer space (missile is 45 deg nose up at over 100,000ft) when shooting from high and fast (30,000ft and 0.9M in the cat) with good TWS tracks on targets at about 60nm, is this expected behaviour? This behaviour results in the missile achieving range of about 30nm. I recorded video of these behaviours while testing against AI H6J bombers that I can post on YouTube if it helps. Unfortunately I'm not running Tacview at the moment. Best regards, BLUEmako
  14. Just a note about my experience with the recent Nvidia drivers (471.68). On two PCs these drivers caused the modules I tested to CTD when loading a mission. Happened consistently with F14, F16, F18 on two pcs. Rolled back the drivers and CTD went away. Hope this helps if you experience the same.
  15. I'm on stable... Hopefully fix is not far away then. ;)
  16. This behaviour has been present in the F14 for me for a few months now. If I get killed in multiplayer then try to respawn in an F14 the game stops responding. I have to force close the game then rinse and repeat. This seems to be similar to the symptoms in this reddit post from April 2021 however my graphics drivers are up to date.
  17. Also seeing this but I can move the switch while on the ground by mouse clicking it in the cockpit
  18. I too am experiencing this. It is not logical to say they are too close to each other, if there's an option to ripple it should not destroy the aircraft... Tested and it seems to happen regardless of speed or altitude when using ripple set with distance 10m. Have not tested other ripple settings.
  19. As noted in the other thread, disabling the Grinelli F-22 mod fixed the engine sounds. Thank you so much for a great mod. The Edge is awesome.
  20. Confirmed that disabling the F-22 fixed the engine sound on the E540. Thanks for the tip.
  21. Great mod thanks guys for your hard work. I have tried it out because I love aerobatics and it flies great. Only niggle is that the engine sounds appear a little bugged. From the cockpit the engine sound only idles, it doesn't change with throttle. From external view the prop sound is correct but the idle sound is present when viewing from behind the 3-9 line. Perhaps it's the exhaust sound not changing with throttle? Hope this post helps. Thanks, Bm
  22. I glad this is not just me. Driving me crazy in the analogue aircraft,.
  23. Okay, further update: reverting to release version did not change the behaviour. Perhaps it is related to an Nvidia driver update or Windows? Anyone else experiencing this behaviour?
  24. Ever since the open beta introduced the new custom save slots for display properties my multimonitor display will not work. I have 2 screens (1x1440p QHD and 1x1080p FHD), the second is used to export the MFDs. The game will start to the menu but will not use the second monitor. It shows DCS on the main monitor only with the aspect ratio compressed. The mouse position sensing behaves like the monitors are working so I have to move my cursor beyond the compressed display to select options. I have tried every combination of rebooting, refreshing the display settings in windows and restarting DCS but it seems to be only randomly that it will correctly detect the second display. The setup was working fine in previous builds. I am now going back to the release client to see if it fixes the issue.
  25. Yep, seems I was using old syntax, my bad. Thanks.
×
×
  • Create New...