Jump to content

Ddaddy

Members
  • Posts

    47
  • Joined

  • Last visited

Everything posted by Ddaddy

  1. I'd like to iterate this. If I had gotten sales notifications in the past I would have bought more modules. As it sits now waiting for a sale on a module... that I'll likely miss again and thus no sale. My experience, ymmv.
  2. Well, got me curious so I did a test on 2.10... updated to 2.11... now DCS crashes during load... off to research and post log file somewhere... add: Ok, got that sorted.... I get about 10% FPS with 4 displays at these settings running Reshade
  3. Curious, anyone ddu'ed video drivers before installing 511? Hope it's ok to post this link, it's nv forum on 511. It may help some find a fix for their system with dcs. https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/481754/geforce-51123-grd-feedback-thread-released-11422/
  4. Yes, I agree CarbonFox, yet another rabbit hole to look in. I am pretty convinced, right or wrong, it's some kind of authorization issue with that 1 file, whether it's the file or windows (because of a coup[le error discriptions). I might just give that win 8 compat a try, ty and watch your 6!
  5. yea, I also updated resahade too and had to manually/remove/insure uninstall of it as their uninstaller missed a couple files. On a slight dif note, you fly f18? Is your map in amp displayed in all range settings still? Mine seems to only work at short range now, not 160 or 80.
  6. Yea, did the graphics... do have one thing funky there... aspect ratio I can't change. at 1.333 and needs to be 4:3 (4646x1080). However displays correctly. I contribute this to 2.7 and it messing up my multidisplay setting. A rebuild fixed the weird Rmfd bloom I was getting in when displayed in either aux display but not in main... Might do a bac of it, uninstall, reg clean and reinstall... even install non beta.... IF/WHEN it starts crashing again. Since 2018 updates have never been an issue except reshade 1 time.
  7. Yea, I got here from that and got interested in the file dates i.e. what 2.7 changed in bin. Just rabbit hole...but one is bound to have a rabbit in it! On another note, I tried to re-register the dx11backend.dll file in win but it fails.... rabbit hole in rabbit hole... likely. edit. and btw, did 3 missions tonight... no crashes on exit...
  8. Ty. Ah, can I presume you did a clean install on the 18th? Anyway this is why I asked since I have a few files from previous install and wondering if that was an issue.
  9. @Fra298In the bin folder, what's the date/properties of dxbackens_mem.dll and D3DCompiler_47.dll?
  10. So 4 times good... then crashes again on exit...
  11. Just did 3 back to back 3 dif maps, no crash... I turned Win Def Private network off. Turned Win Def Private network back on,,, no crash... Def seems to be access issue sometimes! with that backend file... taking a break, gl and will check back later
  12. Been using BN's autoconfig too.... I keep coming back to the dx11backend. Just gave that dll full access on all system/users/etc. still crashing. The darn thing is that sometime sit doesn't! More stuff I've looked at: dxdiag.txt Fault bucket 1632219489306657687, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: DCS.exe P2: 2.7.1.6709 P3: 60adebf9 P4: dxgi.dll P5: 4.9.1.1003 P6: 5ffa0e92 P7: c0000005 P8: 0000000000036c83 P9: P10: Crash report: C:\WINDOWS\SYSTEM32\d3d11.dll # C0000005 ACCESS_VIOLATION at B8606BAE 00:00000000 SymInit: Symbol-SearchPath: '.;d:\Program Files\Eagle Dynamics\DCS World;d:\Program Files\Eagle Dynamics\DCS World\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'Daddy' OS-Version: 10.0.19042 () 0x100-0x1 which this is interesting rabbit hole C:\websymbols*https://msdl.microsoft.com/download/symbols; Microsoft Internet Symbol Server The data you requested cannot be retrieved. You have reached this page because either you or an application that you are running has tried to retrieve debugging data from Microsoft. The requested data is either not available or needs to be retrieved by using the latest Microsoft Symbol Server technology. The data at this site is not accessed from a web browser. Instead, it is accessed by the symbol server technology that ships as part of the Debugging Tools for Windows and Visual Studio. For more information, see Symbols for Windows debugging (WinDbg, KD, CDB, NTSD) and Specify symbol (.pdb) and source files in the Visual Studio debugger.
  13. This may be something... *** WARNING: Unable to verify checksum for dx11backend.dll *** WARNING: Unable to verify checksum for NGModel.dll *** WARNING: Unable to verify checksum for GraphicsVista.dll *** WARNING: Unable to verify checksum for webrtc_plugin.dll *** WARNING: Unable to verify checksum for ed_sound.dll And thinking about replacing ED's dx11backend with an older version I have from 2018.... sounds like bad idea but this still may be the file with issue for us. Off to check these other files first tho
  14. BTW, what video drivers ya running (all with this issue pls reply). I'm on 461.72. BTW, this was a deadend for me (rabbit hole imo). FriendlyEventName=Stopped working ConsentKey=APPCRASH
  15. Ok, I'm looking into it now... just didn't want to waste my time if had already been checked out. Rabbit hole or rabbit.. off I go.
  16. Thanks for replying. Looking at this atm... you done any research on this? The exception code 0xc0000005 indicates a memory access violation
  17. Thanks for the work. Haven't flown DCS in a while and started troubleshooting this myself too. For me It seems random, as in make changes crash, make changes no crash, don't make changes, crash and don't make changes, no crash! With or without reshade also same. I have 2 files that show up in event viewer consistently (replaced yet same). Details: Faulting application name: DCS.exe, version: 2.7.1.6709, time stamp: 0x60adebf9 Faulting module name: d3d11.dll, version: 10.0.19041.746, time stamp: 0xfc177b9d Exception code: 0xc0000005 Fault offset: 0x0000000000016bae Faulting process id: 0x2c08 Faulting application start time: 0x01d7557dee5c425a Faulting application path: d:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll Report Id: 0ac14466-522a-45e6-8887-79192a1c0a52 Faulting package full name: Faulting package-relative application ID: Posting to provide info and hopefully colab a solution. On the good side, at least it's on exit!
  18. The right MFD when displayed on external monitor, either left or right display, has a bloom issue and it doesn't matter what is selected, rdr, hsi, sa, etc it displays the same bloom issue.
  19. The elephant in the room is the toxic environment. As with automobiles, trains, nuclear, space, medicine and about all tech/human discoveries and inventions, the gained knowledge does not come with the wisdom to use it. Thankfully we learned very quick with nuclear but the Japan incident still iterates we are far from masters of it. Social media is no different, has great promise to accelerate improvements of the human condition, but also has the possibility of causing great harm. Finding a place where this toxicity doesn't exist has eluded me. You won't stop intentional weaponization of it, but you do have the choice weather to be a part of the harm caused by those who do weaponize it...that is their intent, to use you to do exactly that, cause harm. Sure ya'll don't care but I'm with G.B. on this.
  20. Yes sir, that would, in hindsight, worked the first time... hehe... I spent a lot of time just looking at stuff like all the dds images trying to find the issue as I like to figure out what went wrong to cause it in the first place, can always speculate like an update did it but knowing is different. Also find it interesting that all the files necessary wasn't extracted. Maybe I just did something wrong and maybe a dev can provide some insight, for those who might get the ac and install it. It really is a good plane to just fly as it requires a more basic flying skill set, imo. But yea, your advice is the best for anyone else having an issue most likely and maybe devs will give it a look for folks installing it in the future as it'd be a shame for some to try installing and be unsuccessful for some reason and just give up and move on. O7 @ MAXsenna and thank you : ) Ah, see your from Oslo! I flew into Bodo a few times catching liberty rides and enjoyed sub hunting and overheads going there. A beautiful Country, the cliffs you see flying in along the coastline is just breathe taking ...cold as heck though! More so than Iceland (home base)! I actually still have a jacket I bought from there and still wear it, holding up well after 35ish years! O7
  21. Update: So deleted FXO and META files. Relaunch and the same. Fired up the mb339 installer, uninstalled the 2.5.5 open beta, rebooted launched mb339 installer and installed 2.5.5 open beta, relaunch and the same. Checked sanity (and autoupdate.cfg)! Opened "Everything" and had search for mb339 files to monitor dynamically, launche mb 339 installer and uninstalled 2.5.5 open beta...umm many files left, launched mb339 installer and uninstalled 2.5.5 release and watched all but 3 files disappear in "Everything", 1 miz file I might have created and 2 lua files that I read and appear to be mappings I did, moved these 3 files to a temp folder in different path root, launched mb339 installer and installed 2.5.5 open beta, launched DCS and the mb339 did not appear as an installed ac, launched mb339 installer and installed release not touching open beta, watched additional files being placed in same correct path, launched dcs, mb339 there, selected and cockpit windows now good! Check sanity again and went to dcs backup on separate drive of stable just prior to going open beta and checked autoupdate.cfg and only plane I got installed was the F15 in stable release. Put lua files back and miz file, relaunched dcs and loaded miz file...was one I created to fly mb339 in PG after PG was released, worked fine, rechecked other mb339 location (cauc) and still good! Bottom line, used mb339 to uninstall the mb339 from BOTH release and open beta, reinstalled both and it fixed my problem (at least my computer issue with it!) Edit addendum: Really is a nice plane to fly, Thank you!
  22. Naw, had just finished a couple F18 missions and just wanted to relax with some real flying a bit before I ended. Will give that a try now since back on, and yea, been a bit since I deleted fxo and meta, should have done it after the latest update... :rolleyes TYVM and grats on the news
  23. I hadn't flown this in a while and decided to go for a nice flight. The cockpit textures are camo and can't see out with some verbiage on the camo texture "missing texture". Couldn't find anything on this issue, so can I assume if I just reinstall it'll be fine? On latest OB ver BTW.
×
×
  • Create New...