BLUEmako

Hi, I'm trying to move my DCS installation back to the stable version by using the "DCS_updater.exe update @stable" command. When I do so I get a "404 not found" message from the updater. Has this functionality been removed? TYIA, BM

Well my release version is still not working. I don't have the hard drive space to have to run the open beta version as well as the release version with all of my modules installed. At the very least the F/A-18 datalink should not be causing ctd when you are using the release client. And is it intentional to allow connection to open beta servers when running the release client?

Okay, I installed the open beta version. I've done a quick couple of tests and I can connect to MP servers and use the F/A-18 datalink without an instacrash. My theory is that the issue is related to some change that has been made with the latest patch and implemented updates in the open beta that are not in the stable release. Joining openbeta servers when using the stable release seems to provoke the issue.

I did notice that the crashes might be related to having a JF-17 in the server mission? Consistent ctd with datalink active when JF-17 are around. Also, I seem to be able to connect to openbeta MP servers even though I am running the main client? Is that normal?

Completely fresh DCS install, everything from saved games deleted and vanilla settings. CPU and GPU are both stock settings.

Couple more log files after deleting fxo and metashaders directories and letting them rebuild. And more confusion. Crashes seem to be server specific. I was able to start datalink fine in one server but then when I went back into growling sidewinder the datalink crash happened again. Attached are two more log files, one for the ok mp server, the other for the crash in the growling sidewinder server. Note memory usage during these sessions got up to 17 GB with almost no paging pool, seemed to be all in the physical RAM. dcs-dl-ok.log.txt dcs-dl-not-ok.log.txt

Tried again after reinstalling all modules I have. Still getting same CTD in MP when using F/A-18 datalink. I have upped my swap file to 16384 MB but no change to behaviour. Attached new log file. dcs-dl-crash.log.txt

I ran a repair. Still the same. I removed all mods, ran cleanup and repair. Still the same. I uninstalled DCS completely. Reinstalled vanilla DCS with F/A-18 as the only module installed. Still instant CTD in multiplayer when activating datalink. Happens in at least two servers. The datalink works absolutely fine in single player. This is only occurring in multiplayer. Some log files attached. Will try to capture another to make sure it's there. BM dcs.log.txt dcs.log.old.txt

I recently purchased the F/A-18. When I try to turn the datalink on n multiplayer I get a freeze and CTD as soon as I hit the on button on the UFC. Is anyone else experiencing this? I couldn't find any other threads...

Okay, looks like the issue was on my end. I logged into DCS today and it ran the updater. Dunno why it didn't update a couple of nights ago or why it didn't warn me I was playing MP with an outdated client... Tested and it now looks like the TID repeater is fine. Thanks for the quick replies Ironmike. Sorry for the inconvenience. And thanks for the great Tomcat. I haven't had this much fun simming since Fleet Defender. Now I just need to learn how to fly it better. BLUEmako

You're welcome. Further info in the other thread.

I did some more testing tonight, I don't think it is TCS/TID selection order dependent. I found that if I select A/A HUD mode before TID repeater, it won't work. If I stay in T/O HUD mode and then select TID, it's ok. When the TID repeater is not working, I get no calls from Jester for any contacts, every other flight with TID functioning I get a lot of calls as soon as I take off. All flights with auto startup, wait for full INS align and Jester calls "ready to taxi" before I release to park brake. I have video captured the TID failing and can send it or upload somewhere if it helps. BLUEmako

I'm still experiencing this issue after the patch. Might be related to selecting tcs repeater before tid. I couldnt get the TID to show even though i could hear jester changing radar settings in flight. Seemed to be ok next startup when i selected tid first.

After autostarting my TID doesnt want to work. Full ins align but then when airborne i cant see TID. its blank. Seems to be since patch. Am i missing something? Is Jester watching tv all the time?

Thanks for the reply. I've used that monitor profile to avoid surround, that part is successful. However I am still getting crashes whenever I enable SLI.

I've been trying to get DCS to run on my 2x GTX 970 SLI and triple monitor setup using Nvidia surround without success. Anytime I enable surround with 2 cards installed the game crashes when loading for a flight. Typical error is display driver failed to load requiring a pc reboot. If i turn off surround i can use a 3 monitor profile but the FOV and viewpoints with default 3 cameras is terrible to use. Is there a way to enable sli without crashing? I am using latest nvidia drivers and win 10 latest updates. Any advice welcome. Thanks

Ok thanks for the reply. I was hoping I could have the GUI on the centre only but sounds like that's not possible unless I run three separate cameras for the separate monitors. A setup option to allow a reduced GUI size would be nice for the ultra widescreen option in the future...

I'm using Nvidia surround to run a triple monitor setup at 5760x1080 windows desktop and 6000x1080 bezel corrected mode in games. Prior to the 1.5.2 patch DCS would start and activate the 6000x1080 bezel corrected resolution. Now the launcher stays in the windows default resolution of 5760x1080. If I try to set 6000x1080, the GUI runs off the screen as the monitor stays at 5760x1080 but the GUI is sized to 6000x1080. If I hit alt-enter to force full screen mode, the game GUI resizes to the correct resolution to match the bezel correction but the mouse reports the position according to the desktop locations which are not bezel corrected. I have to run the mouse off the screen to activate the menu items. When I am in the game flying, I cannot get the game to run at 6000x1080 unless Windows desktop is running at 6000x1080. This did not happen prior to the 1.5.2. patch. It is extremely frustrating to have to reset my windows desktop resolution to get the game to run in the bezel corrected mode. My system is Windows 10, nvidia surround mode.

Not sure why it happened but I've fixed the symptoms. Seems that after applying the patch the drop down selection in the options screen wasn't changing the value for the cockpit language in options.lua. I manually changed it to english and it's all working with the English cockpit now. Strange but true.

The patch filename is: DCS-BS_Patch_1.0.1c_EN.exe Listed as the English version on the DCS home page.

I am having problems with DCS:BS when patching using the 1.01c. Pure vanilla install of 1.00, no problem with using English cockpit setting. As soon as I install the 1.01c patch, the sim no longer recognises the English/Russian setting in the options panel and I am stuck with the Russian cockpit and ABRIS. I can switch the Eng>Russian setting over and over without effect. I reinstalled twice with the same results each time. Pre-patch English cockpit, post-patch Russian cockpit only. Training voice over in missions and menu GUI remain English throughout. I looked through the forum and saw a post talking about a localizer.lua file in \scripts\aircraft\ka50\cockpit however I could not find that file. Should this file be present? Any suggestions to get the English cockpit working are appreciated. I am installing from the Direct2Drive installer files. No mods or config file changes at all. Simulation setting off when installing. My OS is WinXP Pro SP3. TYIA BLUEmako