Zakk

Faulting application name: Launcher.exe_unknown, version: 0.0.0.0, time stamp: 0x4933f34b Faulting module name: SDL_mixer.dll, version: 1.2.8.0, time stamp: 0x4832cba3 Exception code: 0xc0000094 Fault offset: 0x00007796 Faulting process id: 0x115c Faulting application start time: 0x01c98a19023bde60 Faulting application path: D:\Program Files (x86)\Eagle Dynamics\Ka-50\bin\stable\Launcher.exe Faulting module path: D:\Program Files (x86)\Eagle Dynamics\Ka-50\bin\stable\SDL_mixer.dll Report Id: 436359ad-f60c-11dd-ba5a-001fd0d5b004 It appears that it may be a menu GUI problem; I clicked around in the empty box to where I thought the "Instant Action" button was located and was able to start it. It fired up instant action in windowed mode and I was able to fly the chopper. I exited and then the blank menu came back; clicked around a bit more and got an error message :cry: When I start the program I see this below: After I hit the PrtScn button, it also made a screen shot file into BS folder of what I AM SUPPOSE TO SEE! What the HELL? Blah ha ha ha ah hashshshslkdsfkj.....I f-ing tricked the damn thing--2 days of PURE HELL I took my stupid screen shots of the MENU's that I could NOT see in real time and used them as underlays. I was able to get into the OPTIONS menu which wouldn't show either and got the FULLSCREEN check box checked. Was able to lower the MUSIC to OFF. Changed the res to 1600x1050 Clicked the OK button that I couldn't see. and exited. Now when I double click the SP launcher it goes to FULLSCREEN and I can see the GUI MENU. Now I am thinking this may be a RealTek HD Audio problem, or the NEW XFX GTX285 vid card. I really don't want to go BACK and FIND out....but I'll post more because I can't seem to keep myself out of trouble for long. On another note, I did notice some video glitching while in the full screen menu; when I move the mouse around I see long black bars that flash accross the screen....hmmm. There really needs to be a SAFE MODE launcher option in the NEW patch, right? DCS-20090208-183616.txt _LastMissionTrack.trk Systemlog.txt

What was it doing before you fixed it with the reinstallation? I uninstall, delete everything; run CCleaner, and reinstall. Did this a million times, and it still doesn't work. I had an 8800GTS that was working just fine, but got rid of it and now it seems, that my 285GTX with current driver my be the issue.

Installed BS on Vista64 last month and didn't have ONE problem. Upgraded to Win7 Beta, and BS still worked perfect. I am now having the same issue--BS single player will not start--I get a blank dialog box after double clicking launcher icon. This problem started after I did the following: Removed backup hard drive that BS was installed on. Installed NEW drive. Installed NEW mobo. Replaced 8800GTS with 285GTX. Reinstalled BS on new drive, and now it won't run. Have uninstalled, and reinstalled in every partition. The multiplayer starts windowed ok, but I don't have access to the OPTIONS from Single Player. When I try and launch SP it does not generate any logs in the Temp folder; only when I launch MP. At this point I feel it's nvidias latest driver and my 285GTX not working with BS as I have tried everything under the sun. Now what :( ErrorMP.txt DxDiag.txt

I got rid of my 8800GTS and replaced it with a GTX 285; now when I try and launch the game I get a blank box with music. The real funny thing is that there is NO DCS process listed listed in task manager. I can't close the window, only minimize it, but the music keeps playing. Multiplayer launches, and I am able to activate. FSX works; no problems. Running lastest Nvidia drivers on Vista64 with beta upgrade to Win7. This what the error file says in the temp folder: Error running Config/autoexec.cfg: cannot open Config/autoexec.cfg: No such file or directory 2/7/2009 08:58 V808201900 World::LoadPlugins: Loaded plugin module CockpitBase.dll Dispatcher: initial random seed = 5958911 Dispatcher: apply random seed = 5958911 Cosmos: Mission date assigned - Year:2009, Month:6, Day:1 loaded from mission Scripts/World/GPS_GNSS.lua Map objects for beacon site Потийский NOT FOUND! Ojbects created. Map objects for inactive beacon site Мыс Сухумский NOT FOUND! Ojbects created. Map objects for inactive beacon site Мыс Тарханкутский NOT FOUND! Ojbects created. Map objects for inactive beacon site Мыс Железный Рог NOT FOUND! Ojbects created. Map objects for beacon site Мыс Херсонесский NOT FOUND! Ojbects created. Map objects for inactive beacon site Мыс Анапский NOT FOUND! Ojbects created. Map objects for inactive beacon site Мыс Айтодорский NOT FOUND! Ojbects created. Map objects for beacon site Батумский NOT FOUND! Ojbects created. Map objects for beacon site Мыс Фонарь NOT FOUND! Ojbects created. Map objects for beacon site Мыс Евпаторийский NOT FOUND! Ojbects created. Map objects for beacon site Ялта NOT FOUND! Ojbects created. Map objects for inactive beacon site Мыс Кыз-Аул NOT FOUND! Ojbects created. Map objects for inactive beacon site Мыс Кодошский NOT FOUND! Ojbects created. ComplexTask::open_state(). Precached tasks data loading. ComplexTask::load_task_data(). "Follow_Line" task data loaded. ComplexTask::load_task_data(). "Follow_Vector" task data loaded. ComplexTask::load_task_data(). "Follow_Vector_Old" task data loaded. ComplexTask::load_task_data(). "Approach" task data loaded. ComplexTask::load_task_data(). "Cannon_Ground_Attack" task data loaded. ComplexTask::load_task_data(). "Rocket_Attack" task data loaded. ComplexTask::load_task_data(). "Level_Bombing" task data loaded. ComplexTask::load_task_data(). "Dive_Bombing" task data loaded. ComplexTask::load_task_data(). "Missile_Ground_Target_Attack" task data loaded. ComplexTask::load_task_data(). "Missile_Ground_Target_Level_Attack" task data loaded. WARNING: multiple connectors "smoke" in model ".\Bazar\Terrain\Structures\High\TEC_A.lom" WARNING: multiple connectors "RED_BEACON" in model "KA-50" WARNING: multiple connectors "Gun_point" in model "KA-50" WARNING: multiple connectors "MAIN_SPOT_PTR" in model "KA-50" WARNING: multiple connectors "RESERV_SPOT_PTR" in model "KA-50" WARNING: multiple connectors "WHITE_LIGHT" in model "KA-50" WARNING: multiple connectors "RED_BEACON" in model "KA-50" WARNING: multiple connectors "GREEN_LIGHT" in model "KA-50" WARNING: multiple connectors "RED_LIGHT" in model "KA-50" WARNING: multiple connectors "Gun_point" in model "KA-50" WARNING: multiple connectors "MAIN_SPOT_PTR" in model "KA-50" WARNING: multiple connectors "RESERV_SPOT_PTR" in model "KA-50" WARNING: multiple connectors "WHITE_LIGHT" in model "KA-50" WARNING: multiple connectors "RED_BEACON" in model "KA-50" WARNING: multiple connectors "GREEN_LIGHT" in model "KA-50" WARNING: multiple connectors "RED_LIGHT" in model "KA-50" WARNING: multiple connectors "Gun_point" in model "KA-50" WARNING: multiple connectors "MAIN_SPOT_PTR" in model "KA-50" WARNING: multiple connectors "RESERV_SPOT_PTR" in model "KA-50" EagleFM initialize time .. 484.937343 Chunk is not present: ABRIS/Options.lua ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Options.lua Chunk is not present: ABRIS/Database/NAVIGATION.lua ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Database/NAVIGATION.lua Chunk is not present: ABRIS/Database/ROUTES.lua ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Database/ROUTES.lua Chunk is not present: ABRIS/Database/ADDITIONAL.lua ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Database/ADDITIONAL.lua ABRIS load default failed Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Database/ADDITIONAL.lua Chunk is not present: ABRIS/Loader/NAVIGATION.lua ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Loader/NAVIGATION.lua Chunk is not present: ABRIS/Loader/ROUTES.lua ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Loader/ROUTES.lua Chunk is not present: ABRIS/Loader/ADDITIONAL.lua ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Loader/ADDITIONAL.lua ABRIS load default failed Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Loader/ADDITIONAL.lua Cockpit::avDevice::link_all: no such device in hash - 'ARCADE' Cockpit::avDevice::link_all: no such device in hash - 'ARCADE' Cockpit::avDevice::link_all: no such device in hash - 'ARCADE' Cockpit::avDevice::link_all: no such device in hash - 'PADLOCK' Cockpit::avDevice::link_all: no such device in hash - 'MRP' Cockpit::avDevice::link_all: no such device in hash - 'MRP' Cockpit::avDevice::link_all: no such device in hash - 'PADLOCK' Cockpit::avDevice::link_all: no such device in hash - 'MRP' loaded from mission Scripts/Aircrafts/ka-50/Cockpit/ARK/ARK.lua Cockpit: ccClickable.cpp. Custom data unavailable cockpit initialize time .. 11778.710990 loaded from mission Scripts/Aircrafts/ka-50/Cockpit/ARK/ARK.lua cockpit post initialize ..24.645928 Error1.txt

I think you would be better off with this monitor by itself, check your performance and then add to it. http://blog.wired.com/gadgets/2008/01/ces-2008-alienw.html :thumbup:

That's one hell of a setup; hope you get it working to your satisfaction soon. Personally I wouldn't run LESS THAN 4gb ram with Vista. It will probably take another 2 years before we have the desktop hardware to run a configuration like yours. So maybe it's just a matter of time if you have the patience.

Say goodbye to FSX: http://www.gamasutra.com/php-bin/news_index.php?story=21981 :megalol:

What?

"The old Logitech Wingman Force Here's an example on ebay: http://cgi.ebay.com/Logitech-WingMan...3A1|240%3A1318" You couldn't pay me to own that huge hunk of plastic--leave it on eJunk where it belongs--stuff like this is what I just throw in the trash.

Your stick is working FINE--when you press the (T) trim, it trims your flight control surfaces to your last input. What did you expect it to do? This is actually quite useful as now you can actually feel where your stick is instead of having to look at the trim/control box overlay.

Here in the 'good ol US of A' all the game company’s care about are the development of games for the xbox, ps3, and wii at 60 bucks a pop :Flush:. Then they attempt a port of these games to PC in hopes of satisfying the PC market which only makes the pc experience a total train wreck! It's a joke, and the joke is on US--they got your money and you end up with a beverage coaster. And to think, MSFS has been a major contributor for years in flight simulation and they just got blown out by DCS :megalol:. I am looking forward to the warthog and future a/c; now only if DCS could produce a good Nascar sim I'd be in heaven. Congrats to the Ka-50! You guys came through when I thought all hope was lost in a world of console crap--thank you, thank you, thank you!:clap_2:

Because we don't want 3rd party developers benefiting by making a profit and at the same time, ruining this simulation. If you want to make mods and changes, then go ahead and destroy the game at your own risk, but NOT with other peoples money. The only mods I trust are from the developers who created the title--all the rest is crap IMHO.

I have had this issue since day ONE; To correct this problem I hit ESC and then ESC again to bring me back into the cockpit with the mouse view working again. It is a bit annoying to say the least when I try to get my head down into the pit and have to pause the game (ESC) to reactivate the mouse look.

LOL--I remember installing Win95 on my machine back in the day and my friend stuck with Win 3.11 saying it was better. This is the same dude who just asked me the other day "Ohhh, you are running Vista 64 now?" I've had Vista for the last 2 years!

My head is about to SPIN off! The room is moving, and I can't walk in a straight line anymore; I fly choppers all night in my dreams--This is really a good flight sim or I have a serious problem or both. Can't wait for the warthog release!

No and this can be a real problem while flying and using Schval while searching for targets so I would advise using the TTT in Auto-Hover only. The Ka-50 is a bitch to fly and can't wait to get in a fixed wing jet soon; when is the A-10 coming? :pilotfly:

Thanks again Airway; I spotted this myself after I left the post--I must have gotten tired last night after 10 continous of trying to learn ALL many different options--This is an AWESOME simulator that feels like FSX on steroids!

That seems to have been the problem; in GAME mode the A & Q buttons control the collective. Is there a way to FORCE a user created mission into SIMULATION mode? Thanks for your help and quick response!

I created a mission in the editor with one helo (player) and 2 enemy units; selected fly now and the collective will not budge. I've tried every option under the sun and whatever my starting altitude is, that is where it stays. Tried other DCS missions through the editor and they worked just fine. Am I doing something wrong, or is this a bug? :pilotfly: