deadlyfishes
-
Posts
1020 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by deadlyfishes
-
Yes, you need to be on the latest OpenBeta. See here how to convert your install to OpenBeta: https://forums.eagle.ru/showthread.php?t=114030 It is highly recommended to use the standalone version of DCS for best compatibility, stability, and performance. How to convert your Steam install to standalone: https://forums.eagle.ru/showthread.php?t=174776 You can transfer Steam licenses to Standalone as well: https://forums.eagle.ru/showpost.php?p=3751441&postcount=1 -
Not sure about that, I'll have to look into it. Does it happen with other aircraft? Also this an old thread regarding the old TTI versions. Reply to one of the threads in my signature. thanks!
-
UPDATE 03/18/2019 - 1: v1.51c - Further addressed and fixed an issue where EWRS and the MISSION SPAWNING radio menus were not properly working.
-
UPDATE 03/18/2019 - 1: v1.51c - Further addressed and fixed an issue where EWRS and the MISSION SPAWNING radio menus were not properly working.
-
Adding more templates would be fine, but it sounds very specific, like how most missions are designed. In this case it might be better for you to just create your own static layout inside the mission if you wish to do more missions like that. Because of how the spawning works, the layout might not work in certain areas and might bug or glitch through terrain/buildings/objects. Also here's an update: UPDATE 03/18/2019 - 1: v1.51c - Further addressed and fixed an issue where EWRS and the MISSION SPAWNING radio menus were not properly working.
-
Issue was fixed today, see if this new version fixes the issue for you. UPDATE 03/18/2019 - 1: v1.51c - Further addressed and fixed an issue where EWRS and the MISSION SPAWNING radio menus were not properly working.
-
Heyyo! Yeah, there was a "fix" to the menus not appearing for co-op MP players.... There was a nasty side effect where sometimes items weren't lining up properly and aren't reliable as they were before in the first version. The original script we were using for the last year or so basically gives menus to BLUEFOR, but after a few recent updates from ED this year, it broke and stopped giving menus to anyone except the host. In a purely solo situation it's fine but this mission is also great for small MP coop. A fix was added a few days ago, but it's kind of buggy on my end as well. There is another fix I can try, but it might not come out for a few days on my end. If you want a copy of the new mission but with the original menu script (the one that only gives it to host) let me know, I can whip something up temporarily for you. As the post above said, if you edit too many of my units on there, it might cause freezes and crashes since some units are tied to the scripting engine directly.
-
UPDATE 03/14/2019 - 1: v1.51b - Added INS Stored Alignment to all F-14B slots (This significantly shortens the INS alignment time when using "Fine Alignment") - Implemented new F10 Radio Menu logic that refreshes the menu regularly so that new players that join after the host will also have access to the radio menu. - Fixed an issue where the friendly A2A backup units did not have any weapons loaded.
-
UPDATE 03/14/2019 - 1: v1.51b - Added INS Stored Alignment to all F-14B slots (This significantly shortens the INS alignment time when using "Fine Alignment") - Implemented new F10 Radio Menu logic that refreshes the menu regularly so that new players that join after the host will also have access to the radio menu. - Fixed an issue where the friendly A2A backup units did not have any weapons loaded.
-
I never heard of this issue, maybe it has to do with the fact I don't own the module? Worst case, you can always remove that aircraft altogether like you did. ALSO: UPDATE 03/14/2019 - 1: v1.51b - Added INS Stored Alignment to all F-14B slots (This significantly shortens the INS alignment time when using "Fine Alignment") - Implemented new F10 Radio Menu logic that refreshes the menu regularly so that new players that join after the host will also have access to the radio menu. - Fixed an issue where the friendly A2A backup units did not have any weapons loaded.
-
UPDATE 03/14/2019 - 1: v1.51b - Added INS Stored Alignment to all F-14B slots (This significantly shortens the INS alignment time when using "Fine Alignment") - Implemented new F10 Radio Menu logic that refreshes the menu regularly so that new players that join after the host will also have access to the radio menu. - Fixed an issue where the friendly A2A backup units did not have any weapons loaded.
-
New update! OMFG TOMCAT HYPE! UPDATE 03/13/2019 - 1: v1.51 - Added 2 F-14B slots to the mission Note: I'm aware of the F10 Mission Spawning menus not working for anyone except for the host. I have a fix in place, but I need more time to test it to ensure it works properly. For now it's best ran with the host playing instead of using this mission on a dedicated machine if you wish to use the mission spawning and intel F10 menus.
-
New update! OMFG TOMCAT HYPE! UPDATE 03/13/2019 - 1: v1.51 - Added 2 F-14B slots to the mission Note: I'm aware of the F10 Mission Spawning menus not working for anyone except for the host. I have a fix in place, but I need more time to test it to ensure it works properly. For now it's best ran with the host playing instead of using this mission on a dedicated machine if you wish to use the mission spawning and intel F10 menus.
-
New update! OMFG TOMCAT HYPE! UPDATE 03/13/2019 - 1: v1.51 - Added 2 F-14B slots to the mission Note: I'm aware of the F10 Mission Spawning menus not working for anyone except for the host. I have a fix in place, but I need more time to test it to ensure it works properly. For now it's best ran with the host playing instead of using this mission on a dedicated machine if you wish to use the mission spawning and intel F10 menus.
-
New update! OMFG TOMCAT HYPE! UPDATE 03/13/2019 - 1: v1.51 - Added 2 F-14B slots to the mission Note: I'm aware of the F10 Mission Spawning menus not working for anyone except for the host. I have a fix in place, but I need more time to test it to ensure it works properly. For now it's best ran with the host playing instead of using this mission on a dedicated machine if you wish to use the mission spawning and intel F10 menus.
-
Could you try this version for me? I tried a "refresh" script for the menus; https://www.dropbox.com/s/srpwlih7rhm05n3/Through%20The%20Inferno%20%28Georgian%20Coast%29%20v1.50m-test.miz?dl=0
-
I've been working on this a bit, I should have a solution soon enough... The main problem is that the scripting engine has changed a few updates ago and caused this problem. This never used to be an issue a month or two ago... There are workarounds that im playing with. I'll let everyone know when there's a new update. I'm looking to have it figured out before the tomcat comes out next week Sent from my ONEPLUS A6013 using Tapatalk
-
Great report and observation here. I think I'll look into using MOOSE methods to rebuild the menu logic. I've never tested this in MP, which is why I never saw this as a problem initially. Thank you for your information, and I'll try to get this fixed soon in an upcoming update!
-
UPDATE 03/04/2019 - 1: v1.50 - Changed TACAN frequencies of ships/tankers to fix AWACS D/L for the F/A-18C - Added RWR for the MiG-19P - Removed static objects on carriers
-
UPDATE 03/04/2019 - 1: v1.50 - Changed TACAN frequencies of ships/tankers to fix AWACS D/L for the F/A-18C - Added RWR for the MiG-19P - Removed static objects on carriers
-
UPDATE 03/04/2019 - 1: v1.50 - Changed TACAN frequencies of ships/tankers to fix AWACS D/L for the F/A-18C - Added RWR for the MiG-19P - Removed static objects on carriers
-
UPDATE 03/04/2019 - 1: v1.50 - Changed TACAN frequencies of ships/tankers to fix AWACS D/L for the F/A-18C - Added RWR for the MiG-19P - Removed static objects on carriers
-
UPDATE 03/02/2019 - 1: HOTFIX - Fixed a critical scripting error that broke mission spawns. All works now. - AWACS Frequency returned to 251mhz AM as listed in the kneeboard and briefing.
-
UPDATE 03/02/2019 - 1: HOTFIX - Fixed a critical scripting error that broke mission spawns. All works now. - AWACS Frequency returned to 251mhz AM as listed in the kneeboard and briefing.
-
UPDATE 03/02/2019 - 1: HOTFIX - Fixed a critical scripting error that broke mission spawns. All works now. - AWACS Frequency returned to 251mhz AM as listed in the kneeboard and briefing.