pdrgnn

Same here: lua-ED_demosceneAPI.dll Start screen of DCS stop at 10% Item deleted from Kaspersky quarantene.... Repair DCS: no success Should I reinstall everything?

Hi, I have this situation: DCS Open beta 1.5 three days ago update (where can I see the detailed version number of DCS currently installed?) On DCS settings, set screen resolution to 1440x900 Other graphics settings as "Medium" preset Windows screen resolution: 1920x1080 I did this because I was not able to check if I was running windowed or full screen, beeing the two modes, if set the same DCS and Windows resolution, visually identical. I checked that pressing LALT-ENTER switch between the two modes. Then: Flying the A10-C. Everything works fine in windowed mode But when switching to full screen mode, all the clicking areas in the cockpit are not working. Hotas switches and commands work fine. Strange enough the only clickable area in the cockpit is between the ENT and the MK switch of the Up-Front-Controller (UFC), and clicking on it activates the FIRE R ENGINE lever ....!! If I set the same screen resolution (1920x1080) in DCS settings and in Windows, everything works fine. Hope my beta tests will help...!!! Ciao Giovanni My system specs as follow: Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.150928-1507) Language: Italian (Regional Setting: Italian) System Manufacturer: Sony Corporation System Model: SVZ1311C5E BIOS: InsydeH2O Version ChiefRiver.3.72.02.0044R0092C6 Processor: Intel® Core i7-3632QM CPU @ 2.20GHz (8 CPUs), ~2.2GHz Memory: 8192MB RAM Available OS Memory: 8090MB RAM Page File: 4103MB used, 11984MB available Windows Dir: C:\Windows DirectX Version: DirectX 11 DX Setup Parameters: Not found User DPI Setting: 120 DPI (125 percent) System DPI Setting: 120 DPI (125 percent) DWM DPI Scaling: UnKnown DxDiag Version: 6.01.7601.17514 32bit Unicode --------------- Display Devices --------------- Card name: AMD Radeon HD 7670M Manufacturer: Advanced Micro Devices, Inc. Chip type: ATI display adapter (0x6740) DAC type: Internal DAC(400MHz) Device Key: Enum\PCI\VEN_1002&DEV_6740&SUBSYS_90A5104D&REV_00 Display Memory: 4095 MB Dedicated Memory: 1008 MB Shared Memory: 3087 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) Monitor Name: Monitor generico Plug and Play Monitor Model: S24B300 Monitor Id: SAM08B3 Native Mode: 1920 x 1080(p) (60.000Hz) Output Type: HD15 Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,at icfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64 .dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a. cap,atitmm64.dll Driver File Version: 8.17.0010.1124 (English) Driver Version: 8.961.1.0 DDI Version: 11 Driver Model: WDDM 1.1 Driver Attributes: Final Retail Driver Date/Size: 4/25/2012 09:43:11, 1067520 bytes WHQL Logo'd: Yes

This problem disappeared forcing Full Screen (LALT+ENTER)

Hi all, after having hit F6 to follow a missile , I can see it for few seconds, then the screen becomes black, after that I can hear the sound of the missile for few seconds, then everything freeze, tried to press esc, ctrl-alt-canc, but nothing happens. The only way to recover is to hard-shut down the PC with a long press on the power switch. Same after a few second after hitting F7 to view the target. Following are my system specs: Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.150928-1507) Language: Italian (Regional Setting: Italian) System Manufacturer: Sony Corporation System Model: SVZ1311C5E BIOS: InsydeH2O Version ChiefRiver.3.72.02.0044R0092C6 Processor: Intel® Core i7-3632QM CPU @ 2.20GHz (8 CPUs), ~2.2GHz Memory: 8192MB RAM Available OS Memory: 8090MB RAM Page File: 4103MB used, 11984MB available Windows Dir: C:\Windows DirectX Version: DirectX 11 DX Setup Parameters: Not found User DPI Setting: 120 DPI (125 percent) System DPI Setting: 120 DPI (125 percent) DWM DPI Scaling: UnKnown DxDiag Version: 6.01.7601.17514 32bit Unicode --------------- Display Devices --------------- Card name: AMD Radeon HD 7670M Manufacturer: Advanced Micro Devices, Inc. Chip type: ATI display adapter (0x6740) DAC type: Internal DAC(400MHz) Device Key: Enum\PCI\VEN_1002&DEV_6740&SUBSYS_90A5104D&REV_00 Display Memory: 4095 MB Dedicated Memory: 1008 MB Shared Memory: 3087 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) Monitor Name: Monitor generico Plug and Play Monitor Model: S24B300 Monitor Id: SAM08B3 Native Mode: 1920 x 1080(p) (60.000Hz) Output Type: HD15 Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll Driver File Version: 8.17.0010.1124 (English) Driver Version: 8.961.1.0 DDI Version: 11 Driver Model: WDDM 1.1 Driver Attributes: Final Retail Driver Date/Size: 4/25/2012 09:43:11, 1067520 bytes WHQL Logo'd: Yes

Hi, I reinstalled everything (starting from downloading): same corruption. I then installed the Sony Vaio Power Media Dock, which has incorporated a AMD Radeon HD 7670M graphics card: EVERYTHING OK!!! So it seems that the Intel HD Graphics 4000 has some problem with 1.5

Using Intel HD Graphics 4000 Renaming etc ... didn't work Same resolution Temperature OK

Hi, as you can see from the attached pictures, I am experiencing severe graphic corruption. I attach also my system's specs, from DXDIAG. I tested the following: - Various screen resolutions - Full screen mode / windowed (I couldn't see any difference between the two) - Lot of DCS graphics settings (not all combinations, though) - Repair - Reinstall - Only 1 screen, the native one (I usually use 2 screens in a 2 screens configuration (one is the native Vaio screen, the second is a large Samsung) The corruption is visible only at the top of the screen, both in the cockpit view and external view. Looking at the aircraft from top (from top to botton) looks fine. When lowering the view (as in the pictures) the corruption appears. NO MODS INSTALLED :helpsmilie: Any help will be much appreciated....!!!! Many thanks in advance DxDiag.txt

:music_whistling: Since we are now "late 2014", is there any news about? Ciao Giovanni

Thank you for your replies. I imagined that multiple tracking was not allowed... but I was confident that if a way exist, here I could have found the answer. Firing at multiple moving targets is indeed challenging, because after the first strike the remaining targets (tanks in my case) begin to move randomly out of the road...!!! Cheers Giovanni

Hi, I was able to point track a moving target using TGP, and then firing a Maverick to the moving target (it was following the moving target). Is there any way to lock multiple moving targets? (marks?). I tried some procedures but not sucessfully...!! Thanks and best regards Giovanni

Any news re the release date of the new rendering engine? Ciao Giovanni

I think your case is different from mine: I could see targets from far, they disappeared while the distance shortened. In any case your situation has occurred also to me. I suspect that this appens when you move an object to a location where the ground is at an higher altitude than the original spawn location. Try to delete the object and respawn it at the desired location. Ciao

Hi, I noticed that approaching (approx 1000 meters) a target, the TGP image of the target, zoomed in or not, start flashing and then disappears. Not a big problem, firing at the target from adequate distance. When approaching further, the target appears again, but corrupted, same as the post below from Pepec9124. Tested various combination of settings, no results. Any help will be appreciated..!! Thanks Giovanni

Hi, is there any way to modify the default initial setting of TGP contrast and brightness, so that I will never more adjust them at every mission start? Many thanks Giovanni