brunodk

I think it's annoying I can't switch to gunner seat in MP. It gets dull pretty fast when I can only use the hellfire missiles through George.

With AFC and ALT HOLD enabled the AV-8B can't seem to fly straight all the time. It slowly turns in either direction, sometimes more, sometimes less. If the load is asymmetrical the turn is quite significant. How I've tested: Create mission with AV-8B in flight with one waypoint and GPU-12 on the outmost stations. Start the mission and trim the aircraft straight for the waypoint. Enable AFC and ALT HOLD. As the aircraft comes closer the waypoint slowly comes off-center. E.g. the airplane is turning. Replay the mission. Jettison one station and trim the the aircraft for the waypoint. Enable AFC and ALT HOLD. The aircraft comes off the waypoint quite quickly.

I've had the same problem. I've looked into the mission in the mission editor and found the JTAC frequency set to 144 Mhz. After I've set the radio 1 or 2 to 144 Mhz I can now contact JTAC.

I saw the replay. You were flying almost 400 mph and pulling about 7 G, that'll break the wings for sure.

I get the same error from the standard mirror. Just select another mirror from the combobox.

I'm having same issue, the game is much more unstable now. Mostly it's the dcs.exe that's the fault module path, but I've also gotten edTerrain.dll, ZweiBlau.dll, MSVCR100.dll, wRadio.dll, ntdll.dll and lua.dll for the last 8 days. And as Falcon mentions, don't dare command ground units around, I've had continous crashes trying to do that (some units can be commandeered, but some just crashes the game).

I don't think it all can be blamed on the newcomers alone. I mean the game miss very simple but vital functionality for newbies, and it's not very intuitive, hell, when I first tried out multiplayer I spent 10 minutes just trying to figure out how to jump into a plane and start flying! It reminds me when I first tried out Windows 8, where I couldn't figure out how to shut down windows without having to google it. Now the missing functionality: 1. The thing not being able to see keyboard commands when playing (and change them)! It sure was the most annoying part when I first started playing. It's not really a surprise newbies ask these questions when you need to leave the mission, exit the game, start up dcs, check the commands, start up multiplayer and finally join the game again. 2. Why can you jump into planes you don't own? Instead of simply telling the user they must have the selected airplane, they simply get into the plane without a cockpit. Brilliant! :thumbup: 3. Joining the game can be made more simple, for instance, simply add a Fly button, and if no airplane is selected tell the user he/she has to selected an airplane first! Hell now we're at it, what I miss as well: 1. Scrollbar in the chat. 2. Being able to see previous mission messages. 3. Being able to see the damn mouse cursor while reading the briefing. :doh: It can't seriously be that hard to add.

Newspeedy there's a quick solution to the hover dust lag, as I have same problem. Simply delete: ...\DCS World\Bazar\Effects\PFX\high\smokecloud.pfx and the hover dust will no longer be shown. Just remember to delete it after you have applied a new patch.

I tried to re-add the triggers with no effect, it still crashes.

I've tried to run my mission again, and well, now it doesn't crash - very weird! When I made the mission and tried it out, it crashed every single time after about 11 min in-game, but now... nothing. The way I made it crash was simply to pick an aircraft (ka 50 or A-10C) and wait with or without LCtrl+Z for time speed. Why is doesn't happen now is beyond me. *** EDIT *** I'm able to make it crash again. What I did: 1. Deleted the DCS folder in Temp (C:\Users\Bruno\AppData\Local\Temp\DCS). 2. Ran the mission from the ME, selected A-10C Enfield11, switched on the battery, and watched the A-10C clock reach approximately 12:11 (using time speedup) where dcs.exe crashes followed by launcher.exe. How I fixed it: 1. The Q1 Escort group has two "Transmit Message" triggers. I removed them, and now it doesn't crash. NOTE: I've seen the game become unstable before when clearing the Temp folder, but I can't be sure.

Hi. I've created a mission which I have attached. When I try and run the mission, the game crashes after about 11 min (in-game time), and so does the launcher (launcher.exe) that starts up after I've closed dcs.exe due to the crash. I've done it several times. Always the same behaviour. First crash (dcs.exe): Faulting application name: dcs.exe, version: 1.2.5.15865, time stamp: 0x51f13011 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000119930522 Faulting process id: 0x11a0 Faulting application start time: 0x01ce8d3d5bc7f0c6 Faulting application path: C:\Games\DCS World\bin\dcs.exe Faulting module path: unknown Report Id: c2a89e78-f930-11e2-bed1-c86000dd96b0 Faulting package full name: Faulting package-relative application ID: Second crash (launcher.exe): Faulting application name: Launcher.exe_DCS, version: 1.2.5.15865, time stamp: 0x51ee7669 Faulting module name: Effects.dll, version: 1.2.5.15865, time stamp: 0x51ee76f3 Exception code: 0xc0000005 Fault offset: 0x0000000000034a44 Faulting process id: 0x1050 Faulting application start time: 0x01ce8d3d5b0bf221 Faulting application path: C:\Games\DCS World\bin\Launcher.exe Faulting module path: C:\Games\DCS World\bin\Effects.dll Report Id: cf895a20-f930-11e2-bed1-c86000dd96b0 Faulting package full name: Faulting package-relative application ID: COMPLEX.miz logs.zip