abikns

And here we are, another 3 months closer to the 3rd anniversary of this issue. Exporting the IFEI or RWR to a different screen is considered cheating, while my opponents happily fly through my stream of bullets unharmed, because their slow computers or internet connections gives them the advantage of lag. Or they just teleport their little vipers by fast rolling them and getting out of defensive positions by becoming invisible. Adding the needed export lines to the lua code is a huuuuuuge risk, but exporting the DDIs the same way is not, sure. Well, I'm not waiting for the 3rd anniversary, no more passion and support and dollars from me, I'm done with ED and DCS. Over an out!

Yeah, this is getting ridicules, there are several threads about this since 2 years with zero progress. At this point I think the only conclusion is that ED does not care.

I'm glad I stopped building my 2nd simpit, when I realized that this will not be fixed. And I stopped buying modules and maps, of course, no point, if you can't use them. Add all the other problems DCS is facing recently and you can guess, where it is going ...

@BIGNEWY it is almost two years now, could we please get an update on this? Is it really too much to ask?

Thank you for your response Flappie. To check the RAM is always a good idea, when DCS (or other games) crash, I have had that issue several times in the past, but I did a RAM test already and had no errors. I figured it out. I have seen that other people having the same error in the past and it was always related to VR. I'm not using VR, but TrackIR. Here is what I did wrong and what fixed it: Yesterday I copied my TrackIR profile DCS.xml and now I had "DCS.xml" and "DCS - Copy.xml". TrackIR lists two profiles named "DCS" (apparently they use white spaces as delimiter). That seems to not work well. I deleted the copy and the problem is gone. I had to reboot my computer after I deleted the file. Just restarting both, TrackIR and DCS was not sufficient.

DCS is crashing on my newly installed system with: Faulting application name: DCS.exe, version: 2.9.4.53990, time stamp: 0x6628142e Faulting module name: edCore.dll, version: 2.9.4.53990, time stamp: 0x66243424 Exception code: 0xc00000fd Fault offset: 0x0000000000185937 Faulting process id: 0x0x5734 Faulting application start time: 0x0x1DAA10364061E26 Faulting application path: D:\SteamLibrary\steamapps\common\DCSWorld\bin-mt\DCS.exe Faulting module path: D:\SteamLibrary\steamapps\common\DCSWorld\bin-mt\edCore.dll Report Id: 560f7748-1388-40aa-b158-e368ec29da76 Faulting package full name: Faulting package-relative application ID: I checked my drive, no errors. I verified integrity of game files. Checked my DRAM. Have the newest NVidia driver installed. All seems file, but DCS crashes within seconds in a mission/instant action. dcs.log

I have the same problem, since I installed 2.7.4 today. I think the change log said "fixed UDP port error" (or similar). I never had that error before, but now I have it. Going back to the previous version for now.

Good point, I did overlook that little detail. Thank you for your response.

I observe the same behavior, but only in certain maps/scenarios. I recorded two tracks and in both tracks I fly at ~250 knots, ~3000 ft BAR ALT in level flight. Then I put the throttle to idle, drop the gear and set flaps to full and just wait for things to happen. In the Nevada track it does pretty much what I expect: - speed is reducing, nose drops a bit and once the flaps kick in, the nose goes up again In the Syria track things are different: - speed is reducing, nose drops and drops and drops, speed then increases because of the dive, but even with full aft stick, I'm barely able to recover This behavior is repeatable, I tried it several times. I'm using Steam MT preview and the (unmodified) instant action free flight Nevada/Syria. Same behavior with just flaps (not dropping gear). In Syria it seems that the flaps never kick in. Setting the flaps back to auto during the dive results in uplift, which should not be the case. Nevada.trk Syria.trk

Just a coincidence that I looked at it today, because I wanted to ask for an update on this. As MadKreator just stated, more and more servers are set to run pure scripts only and this is really affecting me (and obviously a lot of other people). It is not just a bug or promised and missing feature, it is becoming a "I can't play the game anymore" issue. At this point I have to decide to either play without the simpit that I spent a lot of time and money on building or play with my simpit, but alone. As you probably can imagine, neither of those choices are great. Could you please let us know, what the status of this is? Thank you.

It used to be visible. What's the purpose of it, if it is not visible?

Yes, my game is up-to-date and I used to see the light, before the MT version game out. Am I not supposed to see the light during day landings? Was it dimmed down? I used to see that light from 10 nm away in the past, now I don't see it at all.

I saw that it was marked as fixed, but it is still not working. Not in the "Mission Qualification - Supercarrier CASE I Recovery" "Persian Gulf" at least. I was playing this mission after the last patch and it is still not working on my system.

I tested it in OpenBeta, MT preview with the supercarrier module. The light is off all the time (independent of red, green, yellow).

Does not work since the first multi-core version. Was reported fixed twice, but it wasn't fixed. The topics get closed too, but I'm happy to report it again.

It's disappointing, since we were excited about multicore support, but it's a beta version, so not a big deal. More disappointing is actually that we can not export RWR, IFEI (and probably more) without breaking the integrity check anymore. Is there are reason for that? I wouldn't consider exporting the IFEI in any way cheating, especially since exporting the DDI/MPCD is still possible without breaking the integrity check. That does not make any sense to me. Could you please add those two lines to the scripts, so we can still legally export those? Please? All simpit/cockpit builders are having this problem now.

ED decided for whatever reason to not have viewport exports in RWR, IFEI (and probably more) lua scripts anymore. I can only export left/right DDI and MPCD (F/A-18C) now, without breaking the integrity check. For RWR and IFEI I have to add lines to the mods files, which will break the check. That is very annoying and does not make any sense to me. How is that cheating? Why is the IFEI a problem, but the DDI/MPCD not? With respect to your black screens: the only way to change this (as far as I know) would be to change the order of the screens in Windows. Instead of 1-2-3 you would have to order them 3-2-1 and then start your viewports on x=0 and limit the total width to 2560. Then select this size in DCS for the monitor size: 2560x2040 (1440+600 for the small screens). Now display 1 and 2 are not part of DCS anymore. Screen 1 and 2 should not be black anymore and available for Windows. Disadvantage is, that your screens might be physically on the wrong side, meaning you have to move your mouse to the right, to get to the screen, that in real life is left. Advantage though would be that DCS is not rendering useless screens. I'm not sure, if this has any performance impact, since it is just black, but the total rendering size will be smaller. I guess right now, you use 7920(1920+3440+2560)x2040(1440+600) as monitor size. It might give you more fps, but I'm not sure, but your monitors 1 and 2 should not be black anymore.

I export the Left and Right DDI, MPCD, IFEI and RWR of the F/A-18 via Helios. Since the integrity check was introduced, I can't play on servers with integrity check enabled anymore (unless I throw my simpit away, of course). I tried to export without Helios/changes in the game folder and can export the DDIs and the MPCD, but it seems not to be possible for the IFEI and RWR. Why is that? How is exporting the DDI/MPCD considered ok, but exporting the IFEI and RWR not? As far as I understand, only two lines of lua script have to be added to each instrument lua file by ED, to make it possible and "legal". Add this: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("FA_18C_IFEI", "IFEI") To the "DCSWorld\Mods\aircraft\FA-18C\Cockpit\ScriptsORIGINAL\IFEI\indicator\IFEI_init.lua" and it works. Is this too much to ask?

I have the same problem. I export the Left and Right DDI, MPCD, IFEI and RWR of the F/A-18 via Helios. Since the integrity check was introduced, I can't play on servers with integrity check enabled anymore (unless I throw my simpit away, of course). I tried to export without Helios/changes in the game folder and can export the DDIs and the MPCD, but it seems not to be possible for the IFEI and RWR. Why is that? How is exporting the DDI/MPCD considered ok, but exporting the IFEI and RWR not? As far as I understand, only two lines of lua script have to be added to each instrument lua file by ED, to make it possible and "legal". Add this: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("FA_18C_IFEI", "IFEI") To the "DCSWorld\Mods\aircraft\FA-18C\Cockpit\ScriptsORIGINAL\IFEI\indicator\IFEI_init.lua" and it works. Is this too much to ask?

I can confirm this problem with the F/A-18C DDI Left, DDI Right, MPCD and IFEI.

Hi, I had the same error and I was able to fix it on my system. I'm not sure, if you have the same issue, but I thought I share it here anyways. I had SSA installed and set to 'Start when Windows Starts' and 'Start Minimized in System Tray'. Then I installed the SSA Beta version and it seems, that this is not replacing the old SSA, but installing it in parallel. Now both application try to compete for the same exclusive system resource (port/device), but only one can get it and the second one get the exception, since the resource is already taken. Now you can either remove the old application, end it or unselect the auto start option. When you get this error, check the system tray (bottom right), if you see more than one SSA icons. It worked for me, I hope it works for you too.