AlpineYoda

I can afford to rent a Cirrus, not buy one quite yet. Waiting on those Powerball numbers..... Yes, I have my instrument. Also high performance and complex endorsements. Debating whether I would ever have any use for a multi-engine rating. Flight sim time would take me from the hundreds of hours into the thousands. Not a huge change in insurance rates, but even a few bucks could be worth it.

I've played so many over the years that I can't remember them all, but you never forget your first -- Microprose's F-15 Strike Eagle on the C-64 in early 1986, right after it came out. For you young'ens out there, we had to load the game from a tape deck. That's right, a tape deck. No takeoffs, no landings. Just start in the air and then refly the triangle on the ground that signified your base. Enemies were either triangles to be bombed or an 8-line wire frame see-through airplane. I played that game until the tape deck wore out. That game (and Top Gun) even inspired me to get my congresswomen to help me apply to the Naval Academy, until I learned that you can't fly jets with contact lenses. I have my private certificate these days and I sooooo wish that I could count toward my total time the literally 1,000s of hours I have spent on Strike Eagle I & II, various generations of Microsoft Flight, 2 versions of Microsoft combat sim, a short-lived F-22 "Lightning 2" sim, the original LOMAC, DCS A-10A, DCS A-10C, Falcon 1, 2, 3 (never tried 4 - always heard it was too buggy), X-Plane for my iPad, a shuttle landing sim for my iPad, and probably half a dozen others that I have forgotten, my insurance rates would be far lower!! My Dad recently told me that he has no fear flying with me in actual planes because he saw me growing up flying every sim I could ever find, in all weather, in all combat conditions, and with all manner of battle damage. If I can handle all of that, he says, a Cessna or a Cirrus in "clear & a million" conditions is a piece of cake. A couple of weeks ago, I walked my 6 year old through a DCS World: A-10C mission (one of the target-rich, low defense missions) with my Thrustmaster Hotas Warthog system, MFDs over 8 inch displays, 27 inch main monitor, surround sound, etc. Even if we start simming on 3-D displays or 80 inch monitors, I cannot imagine that he will see as big of a technological jump over the next 25 years as I did watching the evolution from Strike Eagle to DCS. Unless someone can build an affordable full-motion system, home simulators may have gone about as far as they can. Once you reach photo-realism, where else do you go?

I'm sure you thought of this, but in case you didn't, did you update the BIOS? My homebuilt computer uses an Intel DX58SO2 motherboard that had all kinds of issues hanging on boot until Intel posted an updated BIOS file.

Do you have USB monitors for MFDs? I'm trying to find if all these crashes have a commonality.

I found another thread that said to disable the aero interface if using USB monitors, so I did that. Still crashing, but now just back to the debriefing screen, not to windows desktop. It is hard to explain how frustrated I am with ED for shoving everyone into this World system and making it such a pain to use. I'm clearly not the only one with a ton of problems. Can't we just get a 1.2.2 update for standalone Warthog? That worked perfectly well. If it isn't broken, why fix it???

Thanks. That thread is a DCS Warthog thread. My configuration is working just fine in Warthog. I copied my MySetup.Lua file from my Warthog directory to my World directory and it makes World crash. Standalone Warthog runs just fine. Is there something different about World .lua files that I have not found yet?

Thanks for the help. The MCU thing didn't make a difference, but the administrator settings appear to have helped. However, now I have another problem. I spent many hours trying to get the monitor settings just right in Warthog. I copied over my custom .lua file to World, but this is causing another crash. I can make this run in 2560x1440 mode on a single monitor, but I can't use my MFD displays. Is there some change in format from Warthog to World that allows for easy conversion of monitor configurations? My custom .lua file is below. In case the pixel jump from the main display to the MFDs looks weird, I skip over a second main monitor and leave it entirely out of the sim. Thanks again! _ = function(p) return p; end; name = _('MySetup'); Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 1.7777; } } LEFT_MFCD = { x = 4292; y = 10; width = 560; height = 560; } RIGHT_MFCD = { x = 5023; y = 10; width = 560; height = 560; } UIMainView = Viewports.Center

Thanks for the help! Between the election results and last minute studying for my real world FAA private pilot checkride tomorrow, DCS is a low priority tonight. I will do the full re-install tomorrow as instructed and report back in.

yes, 64 bit.

I have the same problem. I posted a report about it here and submitted a ticket a week ago and I haven't heard a word back. I'm really hoping that they are hard at work fixing this and this isn't just poor customer service......

Bump. Any help out there? I sent in a support ticket a week ago and never heard anything back there, either.

I feel your pain. I can't even fly DCS World in the A-10. Crashes 100% of the time on mission load. I'm waiting on a response from the developers and I'm glad to hear I'm not the only one. In your directory, there are crash log files. You might want to upload the text of one to your message in case someone from the company or another knowledgeable person takes a look at your message.

I have never been able to get 1.2.0 to work, so I've been relying on the Warthog standalone to get by. I downloaded and installed 1.2.1 today and got the same result as I always have on 1.2.0, so I figured it was time to ask for help. I'm able to load DCS World, select an A-10 mission, configure my plane/waypoints in the planner, and then it crashes to Windows when I click to fly. System: Windows 7, Intel i7 960 quad core @3.2, 24GB RAM, 64GB SSD boot drive, 2x1TB RAID drives that hold the program, nVidia GeForce GTX 560 Ti, 2 monitors (30" and 24") plus 8" Lilliputs behind Thrustmaster MFDs on USB, Thrustmaster Hotas Warthog, Saitek pedals. Lilliputs, MFDs, HOTAS are all run through a powered USB hub. I've never had a single problem over the last 10 months with regular Warthog, so I know that my system can handle DCS software at medium or better resolutions. In case someone from ED is reading this, I also submitted a ticket to you under my MSCHLACH log-in. The .crash log follows: # -------------- 20121031-215736 -------------- # C0000005 ACCESS_VIOLATION at EFCB34BF 00:00000000 00000000 00000000 0000:00000000 EFCB34BF 001FE1A0 0000:00000000 ?normalizePath@ed@@YAXPEBDAEAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@_N@Z()+1F EB284786 001FE1D0 0000:00000000 ?draw@DXEffect@Graphics@@QEAA_NHW4PRIMTYPE_ENUM@render@@HHHH@Z()+1716 EB2860F4 001FEA60 0000:00000000 ?draw@DXEffect@Graphics@@QEAA_NHW4PRIMTYPE_ENUM@render@@HHHH@Z()+3084 EB29969E 001FEAE0 0000:00000000 ?CreateDXEffect@DXRenderer@Graphics@@QEAAPEAVDXEffect@2@PEBDPEBV?$vector@VDefinePair@render@@V?$allocator@VDefinePair@render@@@ed@@@ed@@@Z()+6E F7B572D0 001FED30 0000:00000000 F7B5754C 001FED80 0000:00000000 F7B57606 001FEDC0 0000:00000000 400DACC8 001FEE50 0000:00000000 400DB43E 001FEF80 0000:00000000 400DABAE 001FF010 0000:00000000 400D86ED 001FF270 0000:00000000 EFCB734A 001FF2A0 0000:00000000 ?onSymbol_@FSM@Common@@AEAAXI@Z()+18A EFCB745E 001FF2F0 0000:00000000 ?checkSymbolsQueue@FSM@Common@@QEAAXXZ()+AE 400DC0F0 001FF350 0000:00000000 40177A5C 001FF3C0 0000:00000000 40178E40 001FF8B0 0000:00000000 4017B81F 001FF960 0000:00000000 7700652D 001FF990 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 7713C521 001FF9E0 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

I just listed the Samsung U70s on eBay if anyone is interested: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=300639891274

I totally agree on their return policy, but I would rather use the Lilliputs than the U70s. Hence the sale. Given that I bought the U70s from somebody in Korea, they are not readily returnable. The U70s are a tiny bit narrower than the MFDs, while the Lilliputs are a bit larger than the MFDs. So, you spend less on the U70s but lose a tiny bit of viewable area. It was a fortuitous mistake.

I have a pair of U70s for sale as well, if anyone wants them. Let's say $175 plus whatever it costs to ship them to you. Both are brand new -- one is still in its wrapping. In the spirit of full disclosure, I unwrapped the other one and was test fitting it against the MFDs and put a very small scratch in the housing. I was checking out the 8" Lilliputs on Amazon and clicked one too many buttons, buying a pair basically by accident, while I was shopping for Christmas presents. So, now I have 2 pairs of displays and I don't need the U70s.