• Content count

  • Joined

  • Last visited

Community Reputation

5 Neutral

About suvo

  • Rank
  • Birthday 07/08/1976

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Profile Information

  • Gender
  1. How to explore ... an airport

    This is where I miss the fsx ultralight trike
  2. Apologies if I don't understand this right. Why would the task manager trick only applicable to SLI configuration? Reading your post what I understand is there seems to be a bug in v3.1 that even after specifying AffinityMask in the cfg file, it is not using the core(s) correctly and we need to reapply this through the task manager once p3d starts running ??
  3. Ezdok with Windows 10 and P3d V3.1/3.0 has something odd. Even if Ezdok runs fine, in the event viewer there are multiple crash logs for ezca.exe more than 10-12 actually and all the reports are identical which is - unknown faulting module, fault module location - x0000000, stack hash error, NTDLL pch crash.. This seems to some memory access violations Looks like ezca.exe is crashing everytime and recovering itself as every crash reports are identical. This problem is getting discussed in simforums as well and seems to be some common issue with windows 10 Although if you can ignore the errors , ezdok otherwise runs fine (v 1.1.87), These crashes doesnt impact ezdok functionality as such Ever since v 1.17 wherein the ezdok adopted DMA (Direct memory access) technology for better performance, it has brought way too many problems with it, almost no security software likes it including the much naive windows defender...
  4. Win10 + MigrationTool + UTII = Done

    I have UT2 installed and running in p3d v3.1 fine... the installation was done using the migration tool.. but i have noticed something weird.. The below is the last entry in my SIMOBJECTS cfg similar to yours.. [Entry.10] Active=True Path=SimObjects\UT2 Aircraft Required=True Title=Default UT2 Aircraft but the entry which the migration tool is adding to p3d.cfg is this.. SimObjectPaths.2=SimObjects\UT2 Aircraft Whereas it should be SimObjectPaths.10. This discrepancy is happening because the SimObjects.cfg file is getting rearranged automatically and the UT2 block is coming at the third position in the file.... and the hence in the P3D.cfg file the numbering is coming as 2 (0,1,2..) as it is numbering in the order of how the blocks are arranged in SimObjects.cfg. Now I have made a change in migrationtool.cfg file to not make any changes to P3D.cfg and have removed the SimObjects entries from the P3d.cfg file and UT2 still runs fine.. Dont quite understand, what is the need for all the Simobjects entries in P3d.cfg. The reason I mentioned this is once, I got a CTD because of fiddling with UT2 menu and i suspect this incorrect Simobjects numbering to be the cause and Migration tool to be blamed more than UT2 itself..