EvilJoven

A dynamic campaign system is sorely needed for DCS. It's what breathes longevity into a platform like this. Take a look at BMS. It's inferior in pretty much every way but people flock to it because of the campaign. The new IL-2 games are also failing because of a lack of things to do and the Lowengrin and Pat Wilson campaign generators for the old IL-2 and Rise of Flight have attracted more players than any aircraft release.

I figured as much. Fortunately a local computer shop had low end 2GB DX11 cards on sale for a very good price. After returning a Displayport to HDMI adapter I'd bought for this PC already it wasn't a high cost at all. Sadly, this doesn't mean the card was *that* cheap, it just means that Displayport to HDMI adapters are terribly over priced.

I can confirm that as soon as I threw in a low end DX11 card the game starts. Hopefully the dedicated server won't need a DX11 card. Fortunately in my circumstance throwing a cheap DX11 card in this thing proved to be a viable option.

On an I5 CPU desktop with Windows 10 but no DX11 capable GPU I'm trying to run the 1.5 beta with 3d disabled (autoexec.cfg contains options.graphics.render3D = false ) for the purpose of a dedicated server. On launch, I get the following crash: Log Name: Application Source: Application Error Date: 10/24/2015 9:57:05 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: NOTTELLING Description: Faulting application name: DCS.exe, version: 1.5.0.46175, time stamp: 0x5628ed1b Faulting module name: d3d11.dll, version: 10.0.10240.16384, time stamp: 0x559f39a5 Exception code: 0xc0000005 Fault offset: 0x0000000000138158 Faulting process id: 0x1658 Faulting application start time: 0x01d10e6c3e23774c Faulting application path: c:\games\dcsworld_beta\bin\DCS.exe Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll Report Id: 62cd2d5b-458c-4265-92dd-16382dcc4d7e Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-10-24T14:57:05.000000000Z" /> <EventRecordID>996</EventRecordID> <Channel>Application</Channel> <Computer>NOTTELLING</Computer> <Security /> </System> <EventData> <Data>DCS.exe</Data> <Data>1.5.0.46175</Data> <Data>5628ed1b</Data> <Data>d3d11.dll</Data> <Data>10.0.10240.16384</Data> <Data>559f39a5</Data> <Data>c0000005</Data> <Data>0000000000138158</Data> <Data>1658</Data> <Data>01d10e6c3e23774c</Data> <Data>c:\games\dcsworld_beta\bin\DCS.exe</Data> <Data>C:\WINDOWS\SYSTEM32\d3d11.dll</Data> <Data>62cd2d5b-458c-4265-92dd-16382dcc4d7e</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Is it even possible for me to do this or is there no way to fix this crash? If it isn't possible, will the actual dedicated server at least be able to run on machines that don't have DX11 GPUs? logs attached, in case they prove useful DCS.openbeta-Crash-20151024-145705.zip

Give server admins the ability to lock it down to the server setting if they so choose. We can already enforce things like map icons, why not this? Also, I think this is a vast improvement over not having smart scaling. It's pretty much impossible to adequately simulate real human binocular vision via a computer monitor when it comes to seeing objects at a distance. I can spot a pickup truck in someone's driveway from FL250 sitting in the passenger seat of a Dash 8 IRL better than I can spot a tank in a parking lot from 10 000' in DCS.

Any chance you have a link to the bug report? I'm curious what the status of it is.

Great mission but we ran in to a bit of a snag. We'd set it to spawn tasks upon request and got orders to hit an AA site with a few SAM launchers and a bunch of stationary cannons. Got there, got talked on by JTAC and I could see the targets but my teammate couldn't. The objects could, however, see him and proceed to try to fill him with lead. Tracers were visible to him but not the emplacements themselves. Any idea what might have caused this?

Last few times I flew it while talking to JTAC but not messing with the CDU. This time I started doing stuff with the CDU and it crashed. All my previous crashes I was working in the CDU while also talking on comms. Maybe that's the problem? Same mission - Shooting Gallery (modified for MP and all other flights removed) with 2 people flying.

My crashes just went away. I think turning simple communications off (something I meant to do but never got around to) seemed to do the trick. Once I turned that off it doesn't appear to matter if it's off or on.

I get the crash about a minute or so after dealing with JTAC.

Please replace the topic line of my other thread http://forums.eagle.ru/showthread.php?t=148011 with this one and then delete/lock this one. Thanks.

You folks getting CTDs while dealing with AI JTAC / ATC via the F key commands? That seems to be what's triggering it with me.

Ran that same mission without talking to ATC / JTAC. No CTD even after engaging a few targets, getting all shot up and landing with a ton of systems failures and an engine out.

Another crash. This time while working with JTAC. Same mission as before, an older copy of the Shooting Gallery mission configured to allow for ramp start. This time I had completely disabled the onboard graphics and was only using my DX11 card. It appears that communication may be a commonality. My first time out in DCS everything was working perfectly until I started communicating with AI ATC / JTAC via the F10 keys. DCS.openbeta-20151002-050643.zip

Were you in the process of talking to ATC or JTAC or something when this happened?