![](https://forum.simflight.com/uploads/theme_resources/set_resources_1/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
Fi5kuS
-
Posts
5 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Fi5kuS
-
-
Hi again. Thanks for quick response :) Ok, then I'll have to do the elimination-method starting with programs/addons that come with AI of some sort.
But again, regarding this topic linked underneath, users report the ai_player.dll CTD but it goes away in the 4.939e version of FSUIPC? Or am I completely misunderstanding the context there?
http://forum.simflight.com/topic/78785-prepar3d-25129430/?hl=ai_player#entry477057
-
Apologies. Fixed in 4.939d, now available.
Pete
There, I knew I saw it somewhere. I just started a new thread about it, but the same issue goes here I guess. Sorry Pete.
I remember I had this issue in FSX:Steam as well. I'm not sure, but I think it went away after installing the latest update of FSUIPC. Now I finally migrated to P3D AND installed the latest hotfix. And frankly, I think the ai_player.dll crash appeared after this. I always install stuff so quickly after a full reinstall of Win7 that I tend to forget, sorry.
Anyways, I'm not using any form of AI traffic programs nor am I using AI traffic (set to 0 % in P3D). I also downloaded and applied the latest FSUIPC 4.939d (unregistered version) but the problem persists. Maybe I'm barking up the wrong three here, but this is my best chance I guess since the previous posters reported the same problems and cured them by installing FSUIPC. Here's a copy of the event dialog:
Log Name: Application
Source: Application ErrorDate: 15.03.2015 23:44:45Event ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer:Description:Faulting application name: Prepar3D.exe, version: 2.5.12943.0, time stamp: 0x54e39da6Faulting module name: ai_player.dll, version: 2.5.12943.0, time stamp: 0x54e39da2Exception code: 0xc0000005Fault offset: 0x00045d19Faulting process id: 0x10fcFaulting application start time: 0x01d05f713e000f5cFaulting application path: D:\Prepar3D\Prepar3D.exeFaulting module path: D:\Prepar3D\ai_player.dllReport Id: dff62111-cb64-11e4-ae65-e03f49b2e014Event Xml:<Event xmlns="http://schemas.micro...08/events/event"><System><Provider Name="Application Error" /><EventID Qualifiers="0">1000</EventID><Level>2</Level><Task>100</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2015-03-15T22:44:45.000000000Z" /><EventRecordID>1985</EventRecordID><Channel>Application</Channel><Computer>Brynjar-PC</Computer><Security /></System><EventData><Data>Prepar3D.exe</Data><Data>2.5.12943.0</Data><Data>54e39da6</Data><Data>ai_player.dll</Data><Data>2.5.12943.0</Data><Data>54e39da2</Data><Data>c0000005</Data><Data>00045d19</Data><Data>10fc</Data><Data>01d05f713e000f5c</Data><Data>D:\Prepar3D\Prepar3D.exe</Data><Data>D:\Prepar3D\ai_player.dll</Data><Data>dff62111-cb64-11e4-ae65-e03f49b2e014</Data></EventData></Event> -
Hi Pete. I recently made the switch to P3D but have encountered a small issue - the ai_player.dll CTD. Some weeks ago when I tested out FSX:SE I also got this error, usually occurring within 5-8 seconds after loading a scenario. I'm not completely sure, but I think the problem went away after installing the latest FSUIPC version. Maybe I'm wrong though, but does FSUIPC contain some sort of fix for this issue? I have the latest version as of 3rd of March, but it doesn't fix the problem in P3D.
I've tried turning AI traffic of completely with no luck either. Moreover, I'm not using any AI traffic programs either. I wonder if it can be the Addon Manager, GSX or some addon-airports maybe causing this CTD for players not using AI traffic programs.
Best regards
Brynjar
Prepar3D 2.5.12943.0
in FSUIPC Support Pete Dowson Modules
Posted
Hi again, Pete.
Yes, sorry, I'm now aware that my issue is not related nor may be fixed by FSUIPC so asking for help here is probably far fetched. I have applied the hotfix which should be 12944 version, but still it seems like my P3D is 12943. Thanks for the observation, Pete. That could well be the issue.