|
Post by Nathan Ford - HJG on Jun 30, 2021 4:40:01 GMT
File was tamper free, but didn’t make any difference so I’ve put back the Uiautomationcore.dll that came with Steam Edition.
Back to square one again 😖. Will keep you updated
Nathan
|
|
|
Post by joscyriacv2 on Jul 1, 2021 16:17:54 GMT
Hi Nathan. Thank you for your reply. I was busy with some personal business hence couldn't find the time to reply. I did some research about the ai_player.dll. Its a quite common error from what I understand. Some forums suggested this maybe due to the FS generating an error when its unable to display AI models. In my case I've got AI switched off. I use vPilot to login to VATSIM which displays VATSIM traffic using the AI library. I trust the error happens somewhere in this process when I'm rapidly changing views. Anyways I'll go with your idea and wait for your file. Thank you Nathan.
Cyriac
|
|
|
Post by joscyriacv2 on Jul 1, 2021 16:21:18 GMT
You may, possibly, have cycled too quickly between views .... rather than at a more relaxed and stable pace. The cause could be as simple as that .... although there could, as I mentioned earlier, be something in what Nathan suggested too. ALSO .... loading a default MSFS aircraft before you add-on aircraft of choice .... then cycling through all of its associated panel views etc .... can, sometimes, help avoid some situations .... and that's despite the fact I don't always do it either. Mark C AKL/NZ Thank you Mark. I suspect this quick changing of views has something to do with the crash. I'll try your suggestions next time.
|
|
|
Post by aerofoto - HJG Admin on Jul 1, 2021 19:29:30 GMT
It's a possibility only .... and just something else you can try whilst nothing more obvious is yet proven.
Not diminishing Nathan's suggestion (in the least) .... as it's still a, if not the, most likely possibility .... given the error messaging you've posted.
Other details of interest to me are ....
Is your B707-420 and B727 (I think you said they were) panels installed inside your aircraft base pack ? .... or have you replicated, in FSX, the FS2004 recommended installation procedure by creating an FSFSCONV folder .... with your B707-420 and B727 panels installed within it .... and the Panel folders inside your base pack then aliased to that FSCONV folder and the panels ? You could try reversing this procedure .... by installing your panels directly inside your B707-420 and B727 base packs in liew of the default Panel folders in either. I very much doubt this'll make any difference to what you've experienced though, but, its still something that can be tried as part of the processes of analysis.
I assume you're using our own panels and gauges.
I also assume your not running anything else (modules/utilities) with your B707-420 and B727. There have, in the past, been a few reported instances where other add-on utilities and modules have apparently caused problems. These sorts of issues have also been known to occur with some systems/installation more than others and aren't, by any means, universal experiences .... according to previous feed back I recall.
Try what I suggested above (it certainly can't do any harm) .... even though I again suspect, in you case at least, Nathan's proposition is probably more likely the cause of you particular issue/s based on what so far been communicated.
Mark C AKL/NZ
|
|
|
Post by Nathan Ford - HJG on Jul 2, 2021 5:00:50 GMT
Yeah not having much luck I’m afraid. Managed a 2 and a half hour flight today by not clicking on any menus and using the “a” key to change between cockpit views. No good for videos or pictures though.
Cheers, Nathan
|
|
|
Post by aerofoto - HJG Admin on Jul 2, 2021 20:26:29 GMT
Still not in don't that Nathan's analysis might have a bearing on this particular reported issue .... but .... I'm going to "TRY TO" call in my heavy weight tech-representative" on this one anyway .... just to see what he can advise .... if anything at all.
Still interested though to know what, if any, add-on utilities/modules are being used .... the like of flight planning, PAX traffic and loading, weather generation etc as (like I mentioned earlier) there "have", in the past been reports of CTD's where it was determined that such add-ons were the likely cause of such issues .... all returning to normal gain "after" they were remove.
In the even any other add-on utilities/modules are being used, then, I'd like to no what happens when they're "removed".
Mark C AKL/NZ
|
|
|
Post by Nathan Ford - HJG on Jul 2, 2021 21:10:32 GMT
Brilliant, thanks Mark. With me, everything had been fine until a couple of weeks ago. I haven’t done anything to the sim, no updating, nothing new, so for me, it is probably a Windows 10 update. FSX-SE is not meant to have this problem as it comes shipped with the working uiautomationcore.dll. The replacement one I trialled, without success can be found… here link Anyone who want’s to try this one, remove your UIAutomationcore.dll from the FSX-SE route directory/folder and put it somewhere safe. I can’t stress this enough, put it somewhere that you can return it to the sim if something goes wrong. When you have placed it somewhere safe, put the one downloaded from NZFSim into the FSX-SE route directory. Restart FSX-SE and right click on the screen to change views, exterior, interior, AI, etc. Keep doing this until either the Sim crashes or (hopefully) it just keeps running.If it crashes, copy and replace your original UIAutomationcore.dll back into the FSX-SE route directory and overwrite the downloaded one. Copy the file into the route directory rather than “cut and paste” you will always have your original backed up somewhere in case something happens in the future. Cheers, Nathan
|
|
|
Post by aerofoto - HJG Admin on Jul 3, 2021 5:04:24 GMT
I sit back .... and often say nothing .... but .... in my doing so I'm always still "ANALYZING". And with my doing so I've constantly noted Nathan that you've done "A FANTASTIC JOB" .... to date .... trying to assist people with their various issues (primarily in regard to FSX) .... and mostly very successfully too I also note. There is (and always will be) the odd issue though that despite the very best of our abilities does arise and that we can't easily resolve. Some issues are unique to particular system configurations. Although we do have a history of being able to successfully resolve most peoples issues .... we can't possibly resolve everyone's particular issue .... only I don't see this (our situation) as being any different for us than is the case with some of the very best of FS payware either. At best we can only do "the very best" we can .... by virtue of our abilities .... and also in accordance with "our knowledge/considerable experience with what we offer" too, but, I do also think we all need to start acknowledging the fact that as OS's advance there'll eventually come a time when what we offer will become less .... and less .... compatible with newer technology .... and that's" a simple fact of life/"A REALITY". "JOCRIAC2" has been most gracious (I wish everyone was like him ) .... and that's to his credit .... and everyone can certainly be assured that "THIS TEAM" will do it's utmost best to try and assist resolving his (and anyone else's) particular difficulty .... simply because this team mostly enjoys what it does and only wants people to be able to enjoy the fruits of its own labors. Mark C AKL/NZ
|
|
|
Post by joscyriacv2 on Jul 4, 2021 18:41:13 GMT
Is your B707-420 and B727 (I think you said they were) panels installed inside your aircraft base pack ? .... or have you replicated, in FSX, the FS2004 recommended installation procedure by creating an FSFSCONV folder .... with your B707-420 and B727 panels installed within it .... and the Panel folders inside your base pack then aliased to that FSCONV folder and the panels ? You could try reversing this procedure .... by installing your panels directly inside your B707-420 and B727 base packs in liew of the default Panel folders in either. I very much doubt this'll make any difference to what you've experienced though, but, its still something that can be tried as part of the processes of analysis. I assume you're using our own panels and gauges. I also assume your not running anything else (modules/utilities) with your B707-420 and B727. There have, in the past, been a few reported instances where other add-on utilities and modules have apparently caused problems. These sorts of issues have also been known to occur with some systems/installation more than others and aren't, by any means, universal experiences .... according to previous feed back I recall. Hi Mark All of may panels have been installed inside the aircraft base pack. I have been following the same procedure back when I was flying on FS9 as well. Yes, It's all HJG panels and gauges. The only other modules/utlities I'm running are vPilot and ActiveSky. Point to be noted is I have done multiple flights on HJG DC-10 without any issue whatsoever.
|
|
|
Post by joscyriacv2 on Jul 4, 2021 18:44:27 GMT
"JOCRIAC2" has been most gracious (I wish everyone was like him ) .... and that's to his credit .... and everyone can certainly be assured that "THIS TEAM" will do it's utmost best to try and assist resolving his (and anyone else's) particular difficulty .... simply because this team mostly enjoys what it does and only wants people to be able to enjoy the fruits of its own labors. Thank you Mark. I'd keep on trying more flights to see if the problem arises again. But I've got some personal stuff going on so I haven't been able to find much time flying. Please do not take much worry regarding my problem. I trust It'll go away on its own very soon. I'm sure your time could be put to more valuable use as you've demonstrated by surprising us with the DM Aircraft. Thank you for that.
|
|
|
Post by joscyriacv2 on Jul 4, 2021 18:45:28 GMT
Restart FSX-SE and right click on the screen to change views, exterior, interior, AI, etc. Keep doing this until either the Sim crashes or (hopefully) it just keeps running.If it crashes, copy and replace your original UIAutomationcore.dll back into the FSX-SE route directory and overwrite the downloaded one. Copy the file into the route directory rather than “cut and paste” you will always have your original backed up somewhere in case something happens in the future. Cheers, Nathan Thanks Nathan. I'll try this once I have some time in hand. Cyriac
|
|
|
Post by aerofoto - HJG Admin on Jul 5, 2021 4:25:04 GMT
I'm not suggesting this's fact or will work, but, some developers are/were (years ago) of an opinion that aircraft base packs should be "as clean as possible". To this extent I've heard of some reputable developers placing panels and sound packs outside their aircraft base packs .... with their base pack folders then aliased to these. I don't see this could make much, if any difference/s, at all, but, thought I'd mention it as something I, at least, have heard over the years .... BUT .... with such numerous variations among both OS's and hardware available today different things can sometimes be noted happen/be experienced on different systems. I don't do this myself though and my own installation/s are strictly in accordance with HJG protocols/recommendations. I'm not suggesting this's a potential cause .... but .... do, a few years ago, recall discussion with a particular group member here (not Nathan ) that ACTIVE SKY .... however innocent it might normally be .... was actually causing issues for the stability of some of our aircraft he had installed at that time. Whenever he didn't use it .... the problem didn't occur. As for the other utility .... all I can suggest is "try flying without it working with the simulation too .... and also without having ACTIVE SKY engaged either" .... and see if that makes any difference/s at all. It may not help though .... but at worst it can certainly do no harm either. Most of the panels we offer feature different programming over different periods of time. That of the DC-10's is much more recent. It's a "POSSIBILITY", but, I reserve my opinion .... simply because I don't want to be prospectively misleading anyone else. Mark C AKL/NZ
|
|