Jump to content

FBDon

Members
  • Posts

    24
  • Joined

  • Last visited

  1. i watched it several times as well. when going to the ground it appears based on your plane that you never pulled up on the stick. Maybe your joystick stopped responding or something but according to the track you never pulled up. If you were in fact pulling up then I would start looking at a bad connection on your joystick.
  2. FBDon

    CTD

    More info on the crashes that I've been having. Happens in several missions, and at different times while playing multiplayer. Below are the most recent two. The first one I had just taken off and was rolling out from banking towards waypoint one... CTD. Last night it was during steady flight at around 14k feet with autopilot on. Nothing special was happening at the time. ------------------------------------------------------ Faulting application name: DCS.exe, version: 1.1.2.1, time stamp: 0x4fa3d0c6 Faulting module name: Weapons.dll, version: 1.1.2.1, time stamp: 0x4fa3d0c7 Exception code: 0xc0000005 Fault offset: 0x0000000000018575 Faulting process id: 0x4b8 Faulting application start time: 0x01cd3a0df005f2da Faulting application path: D:\DCS World\bin\DCS.exe Faulting module path: D:\DCS World\bin\Weapons.dll Report Id: 0a9dbbc8-a603-11e1-b3ab-c860000a7f26 -System -Provider[ Name] Application Error -EventID1000[ Qualifiers] 0 Level2Task100Keywords0x80000000000000-TimeCreated[ SystemTime] 2012-05-25T00:46:20.000000000Z EventRecordID4162ChannelApplicationComputerGamer-PCSecurity -EventData DCS.exe1.1.2.14fa3d0c6Weapons.dll1.1.2.14fa3d0c7c000000500000000000185754b801cd3a0df005f2daD:\DCS World\bin\DCS.exeD:\DCS World\bin\Weapons.dll0a9dbbc8-a603-11e1-b3ab-c860000a7f26 # -------------- 20120525-004619 -------------- # C0000005 ACCESS_VIOLATION at E7998575 00:00000000 00000000 00000000 0000:00000000 E7998575 0031F200 0000:00000000 E798A0AA 0031F320 0000:00000000 E79B990C 0031F370 0000:00000000 E79BB806 0031F3A0 0000:00000000 F6F98361 0031F430 0000:00000000 F6F9882A 0031F480 0000:00000000 3F51F176 0031F510 0000:00000000 3F52170D 0031F590 0000:00000000 3F5B87A1 0031FA90 0000:00000000 3F5BADC7 0031FB40 0000:00000000 7757F33D 0031FB70 0001:0001E33D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 777B2CA1 0031FBC0 0001:00031CA1 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+2 ---------------------------------------------------------------------- Faulting application name: DCS.exe, version: 1.1.2.1, time stamp: 0x4fa3d0c6 Faulting module name: Weapons.dll, version: 1.1.2.1, time stamp: 0x4fa3d0c7 Exception code: 0xc0000005 Fault offset: 0x0000000000018575 Faulting process id: 0x918 Faulting application start time: 0x01cd394f18aa3f2f Faulting application path: C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe Faulting module path: C:\Program Files\Eagle Dynamics\DCS World\bin\Weapons.dll -System -Provider[ Name] Application Error -EventID1000[ Qualifiers] 0 Level2Task100Keywords0x80000000000000-TimeCreated[ SystemTime] 2012-05-24T02:00:39.000000000Z EventRecordID4079ChannelApplicationComputerGamer-PCSecurity -EventData DCS.exe1.1.2.14fa3d0c6Weapons.dll1.1.2.14fa3d0c7c0000005000000000001857591801cd394f18aa3f2fC:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exeC:\Program Files\Eagle Dynamics\DCS World\bin\Weapons.dll425c1127-a544-11e1-97f3-c860000a7f26 # -------------- 20120524-020038 -------------- # C0000005 ACCESS_VIOLATION at EF818575 00:00000000 00000000 00000000 0000:00000000 EF818575 0017F330 0000:00000000 EF80A0AA 0017F450 0000:00000000 EF83990C 0017F4A0 0000:00000000 EF83B806 0017F4D0 0000:00000000 F1708361 0017F560 0000:00000000 F170882A 0017F5B0 0000:00000000 3F60F176 0017F640 0000:00000000 3F61170D 0017F6C0 0000:00000000 3F6A87A1 0017FBC0 0000:00000000 3F6AADC7 0017FC70 0000:00000000 7707F33D 0017FCA0 0001:0001E33D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 771B2CA1 0017FCF0 0001:00031CA1 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 ------------------------------------------------------------------------
  3. FBDon

    CTD

    Duplicated this crash multiple times. Happens at random times in the server. Every time it gives the same error as above with a different memory segment hex code.
  4. FBDon

    Ghost's stuff

    Tracker Natural Point Tracker # 117026 Tracker Natural Point Tracker # 117026 Does that mean you have two TrackIR setups? If so what are they are how much are you looking to get for one of them? Also how much are you asking for the X52? Really just looking to get TrackIR at the moment but if the deal is good might have to bite.
  5. FBDon

    CTD

    Was flying for about an hour in the A-10C. Lots of smoke from dead things. Input new coordinates into CDU for next tasking, banked to line up on waypoint, slewed sensors to SPI... then CTD. Not sure what my framerate was at the time but been running 55-60 most of the day. Attached crash log and dxdiag for system specs. Running my i-5 at 3.7 not the 3.3 that it shows in the report. A couple buddies have had this same error reported in the crash log so decided to post it up. They are working on trying to recreate it. DCS-20120521-031933.zip DxDiag.zip
  6. Np I've ben baby stepped through about a dozen things the last few times online over this week alone so happy to pass on some things to others.
  7. Not sure about the trackir5 but external view would be with the mouse and zoom with mouse wheel
  8. All downloaded and installed. Now just gotta spend about an hour getting my controls setup again... But looks cool. Plus have a few extra planes now if I ever get bored of the A-10. Don't think it'll happen but they are there if I do.
  9. Now the question is what are my options? I've read about and compared.the trackir5 and trackir4 pro but are there other options out there? And does the trackir5 give a huge advantage over the trackir4, basically is it worth the extra 50 bucks?
  10. are you installing from a disk or downloaded file? If a downloaded file was it a fresh down load? Sounds to me like a file corrupted.
  11. Our you could buy a ten dollar belkin serial to usb adapter and not tear apart your old stick.
  12. I've found that autopilot on hold altitude when in a slight bank is my best friend when setting up a target. This allows me to slowly come around on target with enough time to set it up and once set up I dissengage and line up/kill target.
  13. YUP to that one. Such an easy thing to mess up when in the heat of the moment. You hit it once short to go to point track, the you hit it again thinking you held it down long to make SPI but instead it is another short and you just changed back from point to area, and wammo..... your bomb hits about 300 yards long of the targer..... grrrrrrrrrr! Did that several times as well before just taking a wider circuit to the target to give myself plenty of time to get on target and make sure I did it right.
  14. My issues were: not activating the profile right (changed to ccrp) Trying to use them to low... Starting elevation doesn't work. Had to climb to around 7k feet Not following all the required steps to mark the target and get it to stay on target.
  15. Finally made it through east georgia on easy. Been trying to figure out how to fire the gbu-12 and 38 in a mission. Went through the tutorial about a dozen times with no luck putting it to actual practice in s mission. Couldn't remember what button on the key board was what and don't have a hotas. So spent about an hour remapping my stick and got all the needed hotas command put on it using each button as a modifier and then made a cheat sheet of each button. Had a print out if the 20 our so steps for setting up the profile and making the target. Did all my weapon skewing while in looping orbits and only active passed once when wingman got stuck in a radio loop and tried to get him to shut up. Only issue I has was finding the tank column. Nosed the first time and then they ran away. Had to send my wingman after them And I also did a successful landing which is amazing as is. Now to see if I can do it again.
×
×
  • Create New...