Jump to content

deadlyfishes

ED Beta Testers
  • Posts

    1020
  • Joined

  • Last visited

Everything posted by deadlyfishes

  1. The mission contains enemies from different countries and you also play as different countries.... You can easily edit out the units you fight against so that you're fighting specific units making it more closer to fighting allies vs axis Sent from my ONEPLUS A6013 using Tapatalk
  2. Each playable aircraft has two player slots. Add more if needed. As for the units you fight against you can adjust it in the mission editor as the read me file says Sent from my ONEPLUS A6013 using Tapatalk
  3. Did some major troubleshooting here. If I add any bind to Throttle BOTH on my TMWH throttle, the rudder axis line becomes RED and I can't bind it to anything properly. This goes away if I set L/R throttle and remove Throttle BOTH from my TMWH throttle setting. I prefer to use Throttle BOTH since my differential throttles are slightly offset from each other and do not match 100% of the time.
  4. Two more of the same Flight.DLL crashes today on our server, 35 players both times. Looks like the crash happens when people land/launch from the Stennis.
  5. Even deleting the entire CONFIG doesn't work. I still get the same problem after deleting it, making new binds and restarting the game. It works RIGHT AFTER I make the binds, but next time I run DCS, I get the error again. For now, my workaround is a BAT file that deletes the proper Input folder and I just load diff files into the controls for the current session I will play. I'd have to load the diff files again next time, but at least deleting the input folder is automated with my start up of DCS... 100% same issue as this post here; https://forums.eagle.ru/showthread.php?p=3951246
  6. Having this same issue after the DCS 2.5.5.32299 Open Beta update still https://forums.eagle.ru/showthread.php?t=243419 I my workaround process is the same as yours, have you found a fix for this?
  7. I'm only getting this issue with the F-14B. All other modules are fine. TMWH Stick/Throttle TM TFRP Pedals Track IR So here's my troubleshooting process: On DCS 2.5.5.32299 Open Beta - Reinstalled TFRP Drivers/THMW Drivers, updated TMWH Firmware Reinstalled DCS, Repaired DCS, Cleaned DCS, Reinstalled F-14B Module Deleted Saved Games Folder so that a new one is created Once all that is cleaned up and set, I go into the control axis, and remove "JOY RZ" that is already set up for RUDDER and change it to JOY Z. All is good, I can play. However when I quit DCS and come back to the axis bindings I now see that the RUDDER line is RED. I see my control set to JOY Z, but it doesn't do anything. This RUDDER line for other aircraft is fine, and I can properly use JOY Z. The only way I'm able to fix this is to delete the F-14B folder in Config > Input and re-do all my binds again (either manually or loading old ones). This isn't really ideal. I know there are other threads with this issue, but the main problem here is that I've completely re-installed everything DCS and this is on a fresh Windows install as well. dxdiag attached. please let me know if anything else is needed to look further into this issue. DxDiag.txt
  8. I just got another Flight.DLL crash after the last OB update: DCS version is:2.5.5.32299 # -------------- 20190614-190933 -------------- DCS/2.5.5.32299 (x86_64; Windows NT 10.0.17763) C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Flight.dll # C0000005 ACCESS_VIOLATION at 637ED795 00:00000000 SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Matthew' OS-Version: 10.0.17763 () 0x100-0x1 0x000000000004D795 (Flight): ClientData::Position + 0x35 0x00000000000696EC (Flight): LSO::updateLSO + 0x22C 0x000000000006159A (Flight): woATC::controlLanding + 0xC3A 0x000000000005FF90 (Flight): woATC::controlTakeoffAndLanding + 0x70 0x00000000000528DE (Flight): woATC::Control + 0x4AE 0x000000000003E06C (Transport): wAirService::controlService + 0x2C 0x000000000003E8FE (Transport): wcColumn::netDestroy + 0x55E 0x0000000000002D11 (World): (function-name not available) + 0x0 0x00000000000031DF (World): (function-name not available) + 0x0 0x0000000000554352 (DCS): (function-name not available) + 0x0 0x0000000000563AA8 (DCS): (function-name not available) + 0x0 0x0000000000536E34 (DCS): (function-name not available) + 0x0 0x00000000001B012F (DCS): (function-name not available) + 0x0 0x00000000007183D6 (DCS): (function-name not available) + 0x0 0x0000000000017974 (KERNEL32): BaseThreadInitThunk + 0x14 0x000000000006A271 (ntdll): RtlUserThreadStart + 0x21 dcs.log-20190614-190933.zip
  9. Our dedicated MP server crashed twice with Flight.dll. Only started happening after the 2.5.5 update. # -------------- 20190607-082405 -------------- DCS/2.5.5.31917 (x86_64; Windows NT 10.0.17763) C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Flight.dll # C0000005 ACCESS_VIOLATION at 4D93D798 00:00000000 SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Matthew' OS-Version: 10.0.17763 () 0x100-0x1 0x000000000004D798 (Flight): ClientData::Position + 0x38 0x000000000006958F (Flight): LSO::updateLSO + 0xCF 0x000000000006159A (Flight): woATC::controlLanding + 0xC3A 0x000000000005FF90 (Flight): woATC::controlTakeoffAndLanding + 0x70 0x00000000000528DE (Flight): woATC::Control + 0x4AE 0x000000000003E06C (Transport): wAirService::controlService + 0x2C 0x000000000003E8FE (Transport): wcColumn::netDestroy + 0x55E 0x0000000000002D11 (World): (function-name not available) + 0x0 0x00000000000031DF (World): (function-name not available) + 0x0 0x000000000055416E (DCS): (function-name not available) + 0x0 0x00000000005638A0 (DCS): (function-name not available) + 0x0 0x0000000000536C64 (DCS): (function-name not available) + 0x0 0x00000000001B012F (DCS): (function-name not available) + 0x0 0x00000000007181B6 (DCS): (function-name not available) + 0x0 0x0000000000017974 (KERNEL32): BaseThreadInitThunk + 0x14 0x000000000006A271 (ntdll): RtlUserThreadStart + 0x21 Crash zip file attached. dcs.log-20190607-082405.zip dcs.log-20190607-055804.zip
  10. UPDATE 06/06/2019 2: - Added new spawnable units [Fw 190 A8] and the new Fw 190 A8 module as a playable aircraft.
  11. HEY EVERYONE! I just wanted to let you all know, I have officially released the BRAND NEW, 100% REBUILT FROM THE GROUND UP: Through The Inferno: Normandy 1944 (You can find the ED User Files Download link on the first post of this thread.) This mission is now up to the standards of my other Through The Inferno SP missions, with the same and great dynamic gameplay with a very powerful mission customization system and "zeus" spawning system I'll be monitoring this forum, and I'll also take feedback and suggestions on our TTI Discord Server. This is the first release, that I've been testing for sometime with my squadron to ensure the best open-world DCS gameplay possible. As always, thank you all for your support! This re-release of TTI WW2 is made in honor and memoriam for those who fought bravely on the beaches of Normandy, France on June 6th, 1944.
  12. If you a take a look into the zeus script, you need every unit on the map as a template unit set to late activate, so the units in the zeus script with "unit name" need to exist. You also need the moose portable lua loaded on mission start.
  13. UPDATE 06/01/2019 - 1: v1.52b - Fixed an error where some blue units were not spawnable via the 'zeus spawns' - Changed the A2A Intercept mission to spawn 3 bombers that will be somewhat grouped up. They have 3 possible spawn locations on the map that will be chosen at random each time they are triggered. - Added new bombers to the spawnable units list: b1b_blue b52_blue f11a_blue tu142_red tu160_red tu22m3_red tu95ms_red
  14. UPDATE 06/01/2019 - 1: v1.52b - Fixed an error where some blue units were not spawnable via the 'zeus spawns' - Changed the A2A Intercept mission to spawn 3 bombers that will be somewhat grouped up. They have 3 possible spawn locations on the map that will be chosen at random each time they are triggered. - Added new bombers to the spawnable units list: b1b_blue b52_blue f11a_blue tu142_red tu160_red tu22m3_red tu95ms_red
  15. UPDATE 06/01/2019 - 1: v1.52b - Fixed an error where some blue units were not spawnable via the 'zeus spawns' - Changed the A2A Intercept mission to spawn 3 bombers that will be somewhat grouped up. They have 3 possible spawn locations on the map that will be chosen at random each time they are triggered. - Added new bombers to the spawnable units list: b1b_blue b52_blue f11a_blue tu142_red tu160_red tu22m3_red tu95ms_red
  16. Just a quick update here fellas; I'm working hard on making the TTI WW2 Singleplayer mission to be at the same level of depth as the normal TTI Modern missions. With this, I'll also be including a Omaha beach invasion mission where you can choose between attacking the beach or defending it! Here's a little sneak peak on what the mission may look like from the ground:
  17. UPDATE 06/01/2019 - 1: v1.52b - Fixed an error where some blue units were not spawnable via the 'zeus spawns' - Changed the A2A Intercept mission to spawn 3 bombers that will be somewhat grouped up. They have 3 possible spawn locations on the map that will be chosen at random each time they are triggered. - Added new bombers to the spawnable units list: b1b_blue b52_blue f11a_blue tu142_red tu160_red tu22m3_red tu95ms_red
  18. Good to know, since the missions would be very boring without the pack
  19. The date was somewhat arbitrary, but mostly stems from the WW2 version was 1944, so this one was kind of coinciding with that. There wasn't any research going into the date and available weapons. From my understanding at the very least, the aircraft in the mission were in service during that time.
  20. Thank you for the feedback. The modern missions are more popular and take much more time. This will not be an easy feat, but I need to see if there is truly more interest for this. Korea era only has a small handful of units, I'll consider it though. I'm also highly considering NOT using the WW2 asset pack so people do not have to buy anything except for the map to play on this mission. What is your opinion of that?
  21. UPDATE 05/29/2019 - 1: v1.52a - Added ability to STACK ZEUS-Spawned units: - Added MANY more units that can be spawnable via "zeus" map marker spawns. List is on the main post, included as a text file in the zip along with the in-game briefing.
  22. UPDATE 05/29/2019 - 1: v1.52a - Added ability to STACK ZEUS-Spawned units: - Added MANY more units that can be spawnable via "zeus" map marker spawns. List is on the main post, included as a text file in the zip along with the in-game briefing.
  23. UPDATE 05/29/2019 - 1: v1.52a - Added ability to STACK ZEUS-Spawned units: - Added MANY more units that can be spawnable via "zeus" map marker spawns. List is on the main post, included as a text file in the zip along with the in-game briefing.
  24. UPDATE 05/29/2019 - 1: v1.52a - Added ability to STACK ZEUS-Spawned units: - Added MANY more units that can be spawnable via "zeus" map marker spawns. List is on the main post, included as a text file in the zip along with the in-game briefing.
×
×
  • Create New...