Jump to content

Daniel Baker

Members
  • Content Count

    60
  • Joined

  • Last visited

Everything posted by Daniel Baker

  1. Hey Tom, Sorry to hear that, that truly sucks. I'm too lazy to go through the entire thread, but do you have Force ECAM Rendering checked? I reinstalled my entire OS and still had issues (not D3D10Warp.dll, but ntdll.dll) until I checked this off. Cheers, Daniel
  2. Just to add to this: Using A330 1.0.2.0. P3D 4.5 HF3 Active Sky for P3Dv4 Stock turbulence ( Maximum wind turbulence = 100, Turbulence effect scale at 70) Was coming in to Honolulu when I hit fairly heavy turbulence on approach (below 10,000ft, <250 kts). Throttle seemed to "quit" (ie; no thrust, although the engine displays looked like autothrottle was commanding a thrust increase because there was a green arc present; by this I mean the semi-circled arc showing what I believe to be the difference between commanded and actual thrust, if that makes sense) I tried to manually intervene by using the thrust levers, but they suddenly did not work (controllers did not move animated thrust levers anymore). I went into TOGA LK and stalled. I also tried disengaging the A/T button, but that didn't work. The only thing that seemed to move the throttles was using the F1 to F4 throttle keys on the keyboard. Prior to 1.0.2.0 I generally experienced too much airspeed, with the A/T not allowing speed to bleed off. I could intervene in these cases with manual throttle. Do we have suggested turbulence settings in Active Sky for the A330? Thanks, Daniel
  3. Hi Jose, I had been struggling with this issue a lot, and SO FAR, it's been behaving (knock on wood) for the most part. My advice: use the AS Version file (provided earlier in this thread by Otto (mopperle)) and make sure your C++ Redist list matches the one I posted above. That's the first place to start. If not, you'll have to search for each one (some are a bit hard to find with a Microsoft link no longer hosting it, but they are available elsewhere) and install each and every one. The aircraft is extremely sensitive to not having them all installed exactly right, in my experience so far. (Note: I even reinstalled my entire OS and they weren't included in the install process) ALSO: each time I install something (ie; scenery, AI, etc.) I make sure that process didn't affect that C++ Redist list. Hope this helps, Daniel
  4. I agree - perhaps the Windows 10 installers are no longer including these? I think I got them all now? Simconnect, SDKs and Visual C++ Redistributables ------------------------------------------------ Microsoft ESP SimConnect Client v1.0.20.0 - (Version Data: 1.0.20.0) Microsoft Flight Simulator SimConnect Client v10.0.60905.0 - (Version Data: 10.0.60905.0) Microsoft Flight Simulator SimConnect Client v10.0.61242.0 - (Version Data: 10.0.61242.0) Microsoft Flight Simulator SimConnect Client v10.0.61259.0 - (Version Data: 10.0.61259.0) Microsoft Visual C++ 2005 Redistributable - (Version Data: 8.0.56336.0) Microsoft Visual C++ 2005 Redistributable - (Version Data: 8.0.61001.0) Microsoft Visual C++ 2005 Redistributable (x64) - (Version Data: 8.0.61000.0) Microsoft Visual C++ 2008 Redistributable - x64 9.0.21022 - (Version Data: 9.0.21022.0) Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022 - (Version Data: 9.0.21022.0) Microsoft Visual C++ 2010 x64 Redistributable - 10.0.30319 - (Version Data: 10.0.30319.0) Microsoft Visual C++ 2010 x86 Redistributable - 10.0.30319 - (Version Data: 10.0.30319.0) Microsoft Visual C++ 2012 x64 Additional Runtime - 11.0.61030 - (Version Data: 11.0.61030.0) Microsoft Visual C++ 2012 x64 Minimum Runtime - 11.0.61030 - (Version Data: 11.0.61030.0) Microsoft Visual C++ 2012 x86 Additional Runtime - 11.0.61030 - (Version Data: 11.0.61030.0) Microsoft Visual C++ 2012 x86 Minimum Runtime - 11.0.61030 - (Version Data: 11.0.61030.0) Microsoft Visual C++ 2013 x64 Additional Runtime - 12.0.21005 - (Version Data: 12.0.21005.0) Microsoft Visual C++ 2013 x64 Minimum Runtime - 12.0.21005 - (Version Data: 12.0.21005.0) Microsoft Visual C++ 2013 x86 Additional Runtime - 12.0.21005 - (Version Data: 12.0.21005.0) Microsoft Visual C++ 2013 x86 Minimum Runtime - 12.0.21005 - (Version Data: 12.0.21005.0) Microsoft Visual C++ 2019 X64 Additional Runtime - 14.25.28508 - (Version Data: 14.25.28508.0) Microsoft Visual C++ 2019 X64 Minimum Runtime - 14.25.28508 - (Version Data: 14.25.28508.0) Microsoft Visual C++ 2019 X86 Additional Runtime - 14.25.28508 - (Version Data: 14.25.28508.0) Microsoft Visual C++ 2019 X86 Minimum Runtime - 14.25.28508 - (Version Data: 14.25.28508.0) Prepar3D v4 Academic Client - (Version Data: 4.5.14.0) Prepar3D v4 Content - (Version Data: 4.5.14.0) Prepar3D v4 Scenery - (Version Data: 4.5.13.0) Thanks, Daniel
  5. Oh, wow. I thought Windows or the Aerosoft installer would insert everything it needs - my mistake. I'll add those now. Thanks for the help, Daniel
  6. Okay; drive wiped, new Windows 10 installed from scratch. P3Dv4.5 installed from newest installers A330 newest installers FSUIPC5 latest installers Activesky and ASCA installed for weather (newest installers) GSX and GSX Level 2 newest installs FSDreamteam Airports installed in order to have somewhere to fly to: CYVR, KLAX, PHNL, KJFK (all latest installers) Just completed one successful flight, and will continue to fly back and forth between these two without adding anything else. If I get any CTDs I will take Tom A320's advice and start to go back to previous drivers and begin testing again under the same conditions. Just want to be sure the install looks good so far, so I'm attaching the AS_Version and Dxdiag files. Would appreciate if someone from the Aerosoft team had a moment to confirm. Thanks, Daniel AS_Version.TXT DxDiag.txt
  7. Hi Tom, Yes, this is a great idea, thanks. I had the latest drivers (I'm assuming I do now with a new install.) I'm going to try another full install (with as Mathijs mentions, a full wipe of the drive, if I can figure out how) and if I continue to get errors I will try this, absolutely. Thanks Tom! I appreciate that we're having similar issues and keeping each other up to date could provide the breakthrough we need. What do you think of Tom A320's thought above? Would the timing of your CTDs coincide with a driver update? Daniel
  8. Don't think the Agent did that, to be honest. The install was supposed to do that, they told me. Daniel
  9. Okay, I'm going to have them do it again - something must have gone wrong. I wouldn't be totally surprised - I worked with 15 people and most of them are obviously not experts in any way shape or form, as they gave me contradictory advice in a regular sequence it's frankly been a total nightmare. The Level 2 guys seem to know what they're doing, and one is supposed to call me today, so I'll have him advise me and walk me through it. (Yesterday it was a Level 1 guy, working from explicit instructions, who set up the reinstall). Failing that, with your assertions that it would otherwise have to be a hardware issue, I will have to wait until we're out of lockdown here and find a technician to service my computer. I'll bet you it will be one of his most unique assignments ever - please find a hardware issue that only affects one piece of add-on software - but I'm not ruling anything out. If you could try and answer one thing I would be grateful; do you think the method of trying to register the D3D10Warp.dll (taken from this article on the subject https://appuals.com/fix-corrupted-d3d10warp-dll-file/) is a worthwhile indicator of a successful outcome? Thanks, Daniel
  10. I look forward to his involvement, thanks. I will do whatever he recommends. Great idea; I just don't know of any open at the moment. Doesn't make ANY sense to me either... but there are a few of us who are experiencing it, so it's not be unique to my computer. D3D10Warp.dll the only thing I've ever had as an indication of the issue, and that's the indication metric I have of a corrupted D3D10Warp.dll. I've got nothing else to go on - but shouldn't it register properly on a working system? And if yes, and it doesn't on mine, doesn't that indicate it could be the issue? I've also made it clear to Microsoft that we're not done until I get an uncorrupted D3D10Warp.dll. I'm going to continue to hound them for answers. The level 2 technician was puzzled by the D3D10Warp.dll behaviour, and we even tried to replace it with an "uncorrupted" version. That just made my computer hang on start-up. So he said he was glad that he could see it for himself, because it was so strange (and obviously not right)... of course you never get the same person again. Another Level 2 technician will contact me tomorrow, apparently. At any rate, I'll keep you updated, and maybe the others having this issue too will keep updating this thread? Surely something will fall into place if we keep at it? Daniel
  11. Okay... I did exactly as Dave suggested; I spent OVER A WEEK with over 15 Microsoft Virtual Agents (including Level 2 guys), and TOTALLY reinstalled Windows 10, after trying EVERYTHING with them to get D3D10Warp.dll to register (which it wouldn't no matter how many repairs, restores, or in-place reinstalls we did). I stated my problem, insisted that they fix it (and not Lockheed Martin or Aerosoft) - I have been relentless with them, and had them remote in and execute everything (that they could) so that it was done to their satisfaction. I even worked with tech support for my hardware (ASUS, motherboard, etc.) to make sure it wasn't a hardware issue. Now I have P3Dv4.5 (downloaded and installed today, 2020-05-06) and the Aerosoft A330 Professional Installed and nothing else at all. The only other thing was that I installed Simconnect from every folder in the P3D4/Redist I could. I also took Otto's (mopperle) advice and installed to a folder outside Program files, so that now it's C:\Prepar3D v4. I closed down Windows Defender for every install, as well. So... When trying to use CMD to reregister D3D10Warp.dll I get the EXACT SAME ERROR MESSAGE. So that does not bode well, I'm thinking... I have a completely virgin install - now might be the time to ask me to dig into my system, if we're ever going to get to the bottom of this issue. I am willing to let you guinea pig my system, if it helps. I will do nothing more to it until I you say, and you're free to even remote in and poke around, if that helps. Please let me know what I can do to help, Daniel p.s. DXdiag and ASVersionInfo outputs attached. AS_Version_Output.TXT DxDiag.txt
  12. Sorry, that's my confusion. I erroneously thought of them as synonyms/interchangeable. Appreciate the clarification! Looking forward to FLEX implementation Cheers, Daniel
  13. Not according to Emanuel - derate is implemented in the next fix: He confirmed the fix was in the next update - it's apparently an "easy fix". I'm much looking forward to this. Cheers, Daniel
  14. Hi there, I assume you're speaking about derated climb thrust, and not derated climb thrust? Thanks, Daniel
  15. Hi Tom, Thanks for this. Yeah, that's pretty much exactly what I did - except for the fact that I installed the v1.0.0.10 experimental, and maybe I should go back to .8. It worked for awhile and then suddenly started erroring again. But it's good advice to try it again one last time. God help me; looks like the future of my Aerosoft A330 flying is in the hands of Microsoft. I'll try and see how it goes; if it comes down to losing everything else that's already working against the potential of an A330 fix... the math may not work there. It's not the first - nor will it be the last, lol - time I've had to cut my losses with an add-on investment for MFS/P3D. But hopefully an easy fix? At any rate, thanks for helping me as much as you were able to - I appreciate the effort! Sorry, wasn't clear about this; I was suggesting the same issue might be plaguing the A330, with regards to pop-out panels, as the likelihood of a CTD with the A330 for me increased with time in flight. PMDG noted a few people got CTDs after using pop-out panels after a few hours in flight - and I always use pop-out panels in the A330. But please ignore this if you think it's a silly suggestion - I have nothing to base it on. Cheers, Daniel
  16. Hi guys, Unfortunately, after a series of successful flights, I'm back to getting this crash again. I guess I can try and reinstall the aircraft again one last time and see what happens? FWIW; there were only two updates since A330 was last stable; a GSX update and I updated the Navigraph FMS data. Stab in the dark - does this seem oddly similar with the PMDG pop-out PFD error of a few years ago? https://support.precisionmanuals.com/kb/a123/captains-pfd-pop-up-modified-for-ctd-protection.aspx I do use the pop out PFD for take-offs and landings. The longer the flight, the higher the chance of a CTD, I find... Otherwise, I guess I'll contact Microsoft support? Never done this before - is this where I go? https://support.microsoft.com/ And what do I say - I have D3D10Warp.dll CTDs when using P3Dv4 and the Aerosoft A330 Pro? And that I've worked extensively with the Aerosoft team and they believe it's a Microsoft issue - does that about sum it up, or is there anything else I should add? Thanks, Daniel
  17. This is much welcome news, and is my only big sticking point with the plane as it is. So I'm obviously eagerly awaiting the patch that will bring this in. I know you can't talk in absolutes about release dates, but I'm wondering if there is a plan around its implementation? In other words, will the next update be a P3Dv4 update or are there P3Dv5 priorities first? Or maybe it all gets released together? Cheers, Daniel
  18. Hello, So, I did two things, and at this point haven't had any D3D10Warp.dll CTD since. Now... that's only 5 flights, so we'll see what happens. 1) I uninstalled the entire aircraft, and then reinstalled it, making sure all remnants were gone (ie files and folders) 2) I installed the latest supported Visual C++ downloads: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads So far so good... although I am a little sceptical it will continue, as I've had a number of issues with my system (which could very well be at fault) and this aircraft. The testing continues... Daniel
  19. Yes, seems like that's the case. I was hoping to get some idea of what new processes (as you alluded to) the Aerosoft A330 Professional uses that other developers have not yet used, in order to track down whatever is wrong in my system. Unfortunately, there none of the solutions posed online work for me - or else completely shut down my system. I don't know if this means anything at all (it sure doesn't to me) but when I try to reregister the corrupted D3D10Warp.dll (usually step one) it get this message: "The module "d3d10warp.dll" was found but the entry-point DllRegisterServer wasnot found" (pic attached) Not sure where to turn to from here...
  20. … a couple of notes, in case they are of any help whatsoever. 1) I always set an "engine-out" fix in the FMGS. That includes a waypoint/VOR/etc. and a radial to get to it. Once finished the take-off/climb, I usually clear it from the fix page - today I did not. 2) I recently updated SODE to 1.6.8, because I was getting crazy jetway behaviour (ie; when selecting jetways in GSX, they would suddenly point upwards on a bizarre angle). Updating to 1.6.8 fixed this issue. Thanks, Daniel
  21. Whoops - spoke too soon; another D3D10Warp.dll crash Prior to this I had 10 or so successful flights in a row. Attaching ASVersion out put again. Do you require anything else? ASVersion_Output_2020-04-18.TXT Thanks, DanielAppCrashView_2020-04-18.cfg.txt
  22. Update: I could have this finally nailed; two flights down with no crashes, at least. Here are the steps that may have helped. I didn't have C++ 2005 Redistributables in stalled correctly. It also could have been a faulty slopedrwyai.dll file that was installed with the LatinVFR KFLL scenery - they've now updated to correct it. It may have been that my P3D4 folder did not have all the permissions set correctly (read/write etc.) I've also noted that my P3D4 is installed in the wrong folder (the default P3D suggested folder, which is wrong apparently!) but have thankfully not - as yet - had to migrate it to a new one. I'll update if I get the crash again, but fingers-crossed this is now solved. Hope this information helps you kian3454 - apologies if I kind of hijacked the thread, but maybe it was worth it? Thanks very much to Otto and Mathijs for your outstanding help. Cheers, Daniel
  23. Wow, I never knew about this! That's crazy. But thanks very much for making me aware. For now I've changed all the permissions on the Lockheed folder to allow all read/write/modify. Would you happen to know what I do would do about moving the whole thing to its own folder? Is that complicated? (Sorry, I know this is not an Aerosoft issue, but an insight you have would be much appreciated.) I've installed MSV C++ 2005 64bit from this link: https://www.microsoft.com/en-us/download/details.aspx?id=14431 I used the x64 installer - that should be correct, right? One last thing; I saw a defaulting process with slopedrwyAI.dll which came installed with my LatinVFR KFLL software, which they've now updated: http://www.latinvfr.org/forum/viewtopic.php?f=5&t=386&sid=fd4c732b06b4601de294713b293050d5&start=10 Don't know if that's the conflict or a separate issue, but there is an update to apply which addresses this, so I did. Cheers, Daniel
  24. Thanks for your reply. P3Dv4 installed itself - I don't remember asking it to install to a different folder. Not sure what I should do about that? MSV C++ 2005 64bit; is this the link I should use? https://download.cnet.com/Microsoft-Visual-C-2005-SP1-Redistributable-Package-x64/3000-10250_4-10732887.html Cheers, Daniel
  25. Hi Otto, Pleas e find those attached.DxDiag.txt Cheers, Daniel AS_Version_Info_Output.TXT
×
×
  • Create New...