Jump to content

shelt

Members
  • Posts

    169
  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    IL2 1946, Falcon 4 Allied Force, DCS A10C
  • Website
    http://www.sdsquad.com
  1. VR or TrackIR are must haves...welcome to DCS
  2. As a test I lowered my graphic settings for trees and grass, from what I had after the open beta was released. Plus turned off mirrors. When it was first released I had no issues with the settings, but the next couple is where it started. If I did a clean driver install I could get 30-40 minutes before crashing in either single or MP. Then it would get progressively worse to 45-60 seconds then crash. Anyways, have flown all day without a single crash so until I decide to get off my wallet and buy a new video card with more horsepower, I seem to be fine. At least for now
  3. I have tried repair, clean, and delete user files. Even deleted and redownloaded the game for a clean install and still getting the errors. Seems the .dll file which throws the crash is changing. Disabled my anti virus while playing but still get crashes All the logs reference a C0000005 Access_Violation although to different .dll files dcs.log-20180428-234718.zip
  4. I'm having the same issue, but not random. This happens within 20-30 seconds of flying. 2018-04-24 13:01:22.383 INFO EDCORE: C:\Eagle Dynamics\DCS World OpenBeta\bin\NGModel.dll 2018-04-24 13:01:22.385 INFO EDCORE: # C0000005 ACCESS_VIOLATION at E705539B 00:00000000 2018-04-24 13:01:22.389 INFO EDCORE: 00000000 00000000 0000:00000000 2018-04-24 13:01:22.392 INFO EDCORE: E705539B 006FCD38 0000:00000000 C:\Eagle Dynamics\DCS World OpenBeta\bin\NGModel.dll ?getAllShaders@RootNode@graph@model@@QEAAXAEAV?$vector@U?$pair@V?$basic_string@D@ed@@V?$vector@VDefinePair@render@@V?$allocator@VDefinePair@render@@@ed@@@2@@std@@V?$allocator@U?$pair@V?$basic_string@D@ed@@V?$vector@VDefinePair@render@@V?$allocator@VDefinePair@render@@@ed@@@2@@std@@@ed@@@ed@@@Z()+AC3B 2018-04-24 13:01:22.393 INFO EDCORE: 20000000 006FCD40 0000:00000000 2018-04-24 13:01:22.393 INFO EDCORE: 60000000 006FCD48 0000:00000000 2018-04-24 13:01:22.393 INFO EDCORE: E0000000 006FCD50 0000:00000000 2018-04-24 13:01:22.560 INFO EDCORE: Minidump created. 2018-04-24 13:01:22.560 INFO DCS: try to write track file
  5. Brrrrrrrr, Maybe deleting them from the download files would be much quicker for the end user Good stuff, not complaining, but make it for the end user and They do not have to delete files by forum posts
  6. Direct download says 2.4, but when downloaded and opened the folder inside says 2.5 Guess it is hard to keep the version numbers current, given the speed with the releases. Thanks for all the hard work, not concerned with version numbers but it did lead to confusion when a friend said to get 2.5 :)
  7. I had flown several missions with him as well. Sad to hear this. RIP Blooze
  8. shelt

    Auto-Script

    I have it working in 1.5.2 and 2.0 running MIST 4.1.61, so it does work. Not sure why you are having issues? Can you give a little more detail on what problems you are having? Maybe attach a sample mission you have done?
  9. shelt

    Auto-Script

    I've notice an issue when I changed from Activable to Spawngroup. When using Spawngroup, the planes which spawn do not follow any waypoints. They find the closest friendly base and land. Anyone else noticed this? Using Activable the planes follow the waypoints as expected.
  10. Missed it, too bad, think MegOhm drugged my coke...lol Hopefully can catch the next one? or maybe 2.0 is getting close to release (fingers crossed)
  11. Thanks for taking the time to put these together. Much appreciated
  12. Scratch that, operator error on a few things were causing the issue :music_whistling:. I did notice that if infantry is the target, you will get a "No further tasking" message, but will get the MGRS coordinates by using the F10/F2
  13. Megohm and I purchased, Nice plane to fly! Thanks Ells for the effort to put this together.
  14. Nice script, seems to work well. I have built a mission with 4 different JTAC, only one has targets at a time. If the targets are destroyed the JTAC unit is deactivated. Another JTAC will spawn later in the mission. All are given unique names in group and unit, so no problem there. It seems after the mission is run for awhile, the later spawning JTAC will refuse to call targets, but will give the proper coordinates by using the F10 JTAC Status. Any ideas?
×
×
  • Create New...