Wizard1393

PB is Pre Briefed. Not Pull Back.

Question: Can you opt out of installing certain terrains for the Dedicated package? In example, if I want only Caucasus and Persian Gulf, can I decline Nevada and Normandy, to reduce the size of the install? EDIT: Or at least, can I remove terrains directories from the installation, post-install without it causing issues? (as long as I only run Caucasus/Persian Gulf missions offcourse).

Wow now this is awesome for real! Thanks Rik! :) :)

Sweetums!

How would one procure a table with airbase names? Function world.getAirbases() only returns airbase ID's right?

Damn, yeah didn't think of the intermittent extra updater updates. Don't remember if clicking the "Try the HTTP download method" requires an OK click also...

As the title stated, fast moving ground targets. As my second post stated, tried from all directions, perp/front/back, high/low alt, high/low speed, all tests 0 wind. Peoples explanations/posts in this thread about GBU-12 performance seem reasonable, but, my gripe with this would be that I seem to remember the GBU-12's having no issues like this back in the day with the A-10C.

Np :)

Thank you. Finally one answer I was looking for. I know there's not a "bomb energy"-problem as someone said. I've tried everything. Slow and fast, high and low, from all directions. Also no wind. With the same result. GBU-12 won't hit a "fast" moving ground target. Please can anyone else also test and confirm? Set a ground unit, a truck or whatever, to move at 70kmh or whatever their max speed is. Have a JTAC or Lase of choice lase the truck for you. Drop the GBU. Report back. I wonder if this applies only to MP. As in the Laser "lags" a bit and thats the problem perhaps. Must test this in SP....

Maybe it's just an example. But to me it looks like you set it up wrong. You should not set this action on WPT0. Create the action on WPT3, and set switch waypoint 0. This should make the AWACS return to starting pos when reaching WTP3, and thus creating the continuous square route it looks like you want.

So I've been using the GBU-12's quite alot and I've noticed that when dropping them on a lased fast moving target they always fall behind. Often say the first vehicle in a moving column is lased, the bomb will hit spot on the second vehicle. IIRC the GBU's managed to hit lased moving targets pretty much flawlessly back in the day with the A-10C. Did they change the behavior of the GBU's? Anyone else getting these inaccuracies?

I had one too. Originally posted in DCS World Bugs Game Crash section

MP Session. Only me on server. Was flying the F-14B Pilot seat, AI Jester RIO. Had just locked up a helicopter. Then crash to desktop with no error. DCS.log attached. Windows Event Log: Faulting application name: DCS.exe, version: 2.5.4.29585, time stamp: 0x5cadab20 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000e0d5c5e8 Faulting process id: 0xae8 Faulting application start time: 0x01d4efd239a136f5 Faulting application path: F:\Eagle Dynamics\DCS World\bin\DCS.exe Faulting module path: unknown Report Id: c7506cb8-db99-478f-9b88-a481131d579a Faulting package full name: Faulting package-relative application ID: dcs.log.txt

"AutoIT" is another automation tool that could probably work until a silent update command is available. Very easy too. And freeware.

Also, don't know if they meant that the OB patches will be montly now, or just that there will only be Hornet updates every second OB patch...

The Su-27 is like the F-15, but with A2G capabilities. There is also English cockpit mod for the Su-27. I'd say, if you're thinking about getting an FC3 Standalone module, like the F-15 or Su-27, I'd say better just get the full FC3. Then you get all the "simple" aircraft without clickable pits if you're not into that.

Yes. I believe F5 is the "Closest Aircraft View" and it will padlock your view on the closest aircraft.

dcs.log attached. Event Viewer log item: Faulting application name: DCS.exe, version: 2.5.4.29079, time stamp: 0x5c9bcc0c Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000e13575b8 Faulting process id: 0x13b0 Faulting application start time: 0x01d4e7fd7b24c805 Faulting application path: F:\Eagle Dynamics\DCS World\bin\DCS.exe Faulting module path: unknown Report Id: 869ab08c-d90b-47ea-87ab-00c66e2d65c3 Faulting package full name: Faulting package-relative application ID: EDIT: Happened while flying the F-14 dcs.log (2).txt

dcs.log attached. Event Viewer log item: Faulting application name: DCS.exe, version: 2.5.4.29079, time stamp: 0x5c9bcc0c Faulting module name: WorldGeneral.dll, version: 2.5.4.29079, time stamp: 0x5c93a451 Exception code: 0xc0000005 Fault offset: 0x00000000000345a9 Faulting process id: 0x2238 Faulting application start time: 0x01d4e6e1582130f1 Faulting application path: F:\Eagle Dynamics\DCS World\bin\DCS.exe Faulting module path: F:\Eagle Dynamics\DCS World\bin\WorldGeneral.dll Report Id: 24cf7b6b-9a16-44eb-8d14-7cd06c25584b Faulting package full name: Faulting package-relative application ID: EDIT: Happened while flying the F-14 dcs.log.txt

Are you using the "High" preset in game? Grimes example only modifies the High preset. If you're on Extreme or Ultra, nothing will be affected. To change the top three presets with this setting put below lines in autoexec.cfg: options.graphics.Camera.High.dynamic = {300, 60000} options.graphics.Camera.Ultra.dynamic = {300, 60000} options.graphics.Camera.Extreme.dynamic = {300, 60000}

You need to assign the airbase to your coalition also, for rearm to work. As in blue or red.

Agreed. Texture resolution usually does not impact FPS much at all, only uses more VRAM/RAM on High.

I've got a GTX 980 playing on a 1080p monitor and TrackIR and get very descent performance. Yes, it takes a bit longer than other modules to load into the cockpit, but other than that, it's all fine in my end. Was in on a ~16 player F-14 Intro mission last night and all went well, performance wise that I know of. I heard a couple of moans about low FPS for VR users though.

I got the first issue there yesterday. The lever only moved fully aft when pushed down. Didn't get the snap to full forward though. It seemed a little finicky that lever.

+1 would use this option.