|
Post by aerofoto - HJG Admin on Nov 21, 2018 12:58:31 GMT
That´s what we take pride in "trying" to do here "VITOR SBNF" Get back to us .... when you can Mark C BOG/CO
|
|
|
Post by Vitor (SBNF) on Nov 21, 2018 22:03:20 GMT
I'm trying to fly the 707 in a new and clear installation of FSX-SE. All my attempts where with the same texture: Beta Cargo 2004 (PP-BRR)
Today I installed two new repaints: Panam 1964 N799PA and Varig 1966 (PP-VJK)
Both, Panam and Varig worked perfectly. Of these three, Beta Cargo is the only one that uses the model 323C_S2HK. Maybe we'll have a clue to find the problem.
Personally I'm happy to know that I can flyy with other repaints and I do not mind not flying with the Beta Cargo.
Thanks for the quick response!
|
|
|
Post by aerofoto - HJG Admin on Nov 21, 2018 23:14:02 GMT
I´ll have a look at the BETA -320C texture .... and see if there is a texture formatting issue. I can´t imagine why the 323C S2HK model (husk-kitted AA B707-320C cofiguration .... engine pylons with just 2 turbocompressors only) .should present any difficulties, as opposed to any of the others, because they´re all compiled the same way, and the -320C S2HK model is quite extensively used among our post 1984 B707-320C liveries. "IF" .... the CTD occurs when you select the this texture to load into FS, then, that could be indicativbe of a texture formmating issue .... I´ve seen this particular movie before I can see your email address, so, may send you a replacement BETA -320C textures to try out .... if I think it relevant to do so Mark C BOG/CO
|
|
|
Post by aerofoto - HJG Admin on Nov 22, 2018 0:48:48 GMT
WELL .... I´ve downloed the BETA CARGO B707-323C texture and had a look at it .... and its´supprting CFG data too. I couldn´t find anything wrong with either .... BUT .... I converted the texture BMPs from their original DXT3 to a "32-888 no mips" format anyway. I´m using the same B707-320C S2HK model .... and B707-320C FDE .... and with our current "B707-320C AA 1965" panel (thi´s the correct panel version for this aircraft .... featuring 2, and not 3, turbocompressors as per the AA configuration). "Everything" seems fine to me me and as is illustrated below .... No CTD, at all, was experienced in my case .... but .... as I mentioned earlier within this thread, we can´t guaruntee everything we produce will work faultlessly in the case of everyone´s installation .... simply due to the huge variation that exists between systems and H/W today. I´m going to send you (to your forum registered email address) the BETA CARGO B707-323C texture I´ve reformatted this evening. I don´t expect it might change anything in your particular case though, but, there´s certainly no harm in trying it .... and which is what I want you to do .... and to report back "here) after having done so. Mark C BOG/CO
|
|
|
Post by Vitor (SBNF) on Nov 22, 2018 22:52:59 GMT
I'm glad to inform that flight BET1703 landed successfully in Guarulhos Iternational Airport, coming from Manaus in an uneventfull and loudy flight.
Your texture pack worked perfectly.
Thanks for all the effort.
|
|
|
Post by aerofoto - HJG Admin on Nov 22, 2018 23:57:45 GMT
That´s "good news" As there was nothing wrong with the original DXT3 texture BMP´s .... so far as my analysis could determine .... your experience could have been generated by the way that originally formatted texture interacted with your own system (for this reason I won´t yet recommend the currently downloable file be replaced unless any further similar report/s is/are received) .... since different things can be experienced on differeent systms. My converting those texture BMP´s to a "32.888 no mips" format obviously seems to have done the trick for you then in your particular case) .... but .... this action might not be necessary in someone else´s case ( .... it´s just "one of those odd things" whicha can, and sometimes does, happen. Enjoy the HJG B707/B720 simulations .... and which, incidently, are scheduled for an FDE and audio upgrade in the not too distant future. Mark C BOG/CO
|
|
|
Post by joscyriacv2 on Jun 28, 2021 19:22:07 GMT
Well I too have a similar problem. Flying the Boeing 707-420 Air India colours. Departed VOMM and while changing views from outside to inside about FL200, the sim CTDs. This happened twice, both after departing VOMM and around the same altitude while changing views. Today while flying the Boeing 727-200 American Airlines colours, the sim crashed again while changing views. This was after about 1.5hrs of cruise. Now i understand both the 707 and 727 panels were built for FS2004 and may be compatible with FSX. I'd like to know if there's any fix for this. I'm sure if I have flown for 2hrs without any trouble then this may not be about compatibility. Running FSX:SE on a Win 10 system. Requesting your ideas on this. Thank you.
|
|
|
Post by aerofoto - HJG Admin on Jun 28, 2021 19:51:03 GMT
The problem with CTD's is there's sometimes "a zillion things" can contribute to cause such .... making trouble shooting them "extremely difficult". As is evident during my B707 FDE upgrade presentation prior to Christmas .... I flew the AIR INDIA B707-420 (one of them at least) during/as part of that exercise and without any problems at all .... tonymadgehjg.proboards.com/thread/9822/b707-720-modificationsBoth our B707's , and the B727's we host too, are FS2004 native .... but .... they're are also "FSX PORTABLE" .... as are their panels/gauges and sound packs too (separate F2004 and FSX specific sound packs are provided for both of these simulations). Questions I need to pose are .... - When you loaded both simulations in to FS did you start with a default aircraft first .... prior to selecting your B707, and/or B727, of choice ? - When you eventually loaded you B707, and/or B727, of choice into FS did you cycle through each of the interior panels views .... and did you also cycle between interior and external viewing modes prior to commencing your flight ? Ordinarily one shouldn't need to do either of the above (even I don't do it sometimes .... but .... other times I do), but, doing so can assist avoiding unusual issues. - Are you running any other non-HJG supplied utilities, and or modules, with either simulation ? FYI .... the CTD reported in regard to the above-mentioned BETA CARGO B707-320C (during 2018) was definitely a "texture formatting issue" (the odd file can get through our quality control system as that particular case proved) since that file apparently CTD'd "the moment was loaded into FS", but, which doesn't seem to be the case in your particular case, so, I wouldn't be inclined to draw upon any parallel conclusion/s with this earlier report. As I said CTD's are "EXTREMELY DIFFICULT" to try'n troubleshoot .... and just because one person experiences such with a particular file doesn't mean everyone else will. Really need a bit more information than you've provided .... particularly in regard to the questions I have raised Mark C AKL/NZ
|
|
|
Post by Nathan Ford - HJG on Jun 28, 2021 21:43:33 GMT
The interesting thing is this has started happening to me in the last couple of weeks with FSX-SE on WIN10 64bit and not just with HJG aircraft. I have a feeling that an update that came through a couple of weeks ago may have screwed things up.
I’m still investigating and will keep you updated. It’s almost like the “UIAutomationCore.dll“ fix no longer works 😳
Cheers, Nathan
|
|
|
Post by Nathan Ford - HJG on Jun 28, 2021 22:13:02 GMT
Can you looked at your computer's Events Viewer to look for the "Faulting Module" that is causing FSX to crash….
Control Panel-> Administrative Tools-> Event Viewer, select Custom Views-> Administrative Events. One of the listed events will be for your CTD. The "Faulting Module" should point to the problem area.
Tell us what the Faulting Module is! That will point us in the direction of the proper error, aiding in troubleshooting
BELOW IS A SAMPLE OF WHAT YOU MIGHT SEE!
General Tab: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: This is what we need to know! Exception code: 0xc0000005 Fault offset: 0x0000ee3a Faulting process id: 0x748 Faulting application start time: 0x01ce0253dc4b69d4 Faulting application path: R:\\FSX\\fsx.exe Faulting module path: R:\\FSX\\window.dll Report Id: 9caf77b4-6e50-11e2-8570-3085a99825d1
If there is not one listed: Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000, you will need to do as previously noted
Nathan
|
|
|
Post by aerofoto - HJG Admin on Jun 28, 2021 23:10:21 GMT
And just for everyone's comfort (and despite the fact this/what I'm about to say hasn't been suggested) .... We/HJG have made no unotified alterations to either our B707's or the B727's we host.
Our last B707 edits (FDE improvements, panel sounds volume reductions, and new sound packs .... nothing else though) were applied during mid-year during last year and prior to their December/Christmas last year release.
And our last B727-200 (only) edits (FDE improvements, panel sounds volume reductions, and new sound packs also .... again nothing else though) were applied mid-year during 2015 and prior to their October 2015 release.
Nathan could well be onto something
Mark C AKL/NZ
|
|
|
Post by joscyriacv2 on Jun 29, 2021 2:51:02 GMT
Questions I need to pose are .... - When you loaded both simulations in to FS did you start with a default aircraft first .... prior to selecting your B707, and/or B727, of choice ? - When you eventually loaded you B707, and/or B727, of choice into FS did you cycle through each of the interior panels views .... and did you also cycle between interior and external viewing modes prior to commencing your flight ? Ordinarily one shouldn't need to do either of the above (even I don't do it sometimes .... but .... other times I do), but, doing so can assist avoiding unusual issues. - Are you running any other non-HJG supplied utilities, and or modules, with either simulation ? Hi Mark. Thank you for your reply. - No, I didn't load the default Cessna first. I loaded the aircraft directly from the startup menu. I always do that. -Prior to commencing my flight, I haven't purposefully cycled through all the interior panel views. But I would have definitely done so for starting up of the aircraft and operating the controls/switches and all that. Yes, prior to commencing flight I have cycled between cockpit, VC and spot views. - I am running Active Sky X addon for live weather and also vPilot client for connecting to VATSIM. Both of these clients make use of FSUIPC to communicate with FS. All the three times the CTD happened, I was quickly cycling the views from interior/exterior for the purpose of taking screenshots. If i remember correctly my last memory before the CTD would be seeing the spot view. Hope this info helps. Thank you
|
|
|
Post by joscyriacv2 on Jun 29, 2021 2:59:15 GMT
Can you looked at your computer's Events Viewer to look for the "Faulting Module" that is causing FSX to crash…. Control Panel-> Administrative Tools-> Event Viewer, select Custom Views-> Administrative Events. One of the listed events will be for your CTD. The "Faulting Module" should point to the problem area. Tell us what the Faulting Module is! That will point us in the direction of the proper error, aiding in troubleshooting Hello Nathan. Thank you for your reply. Here's what I have observed after following your directions: Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a Faulting module name: ai_player.dll, version: 10.0.62615.0, time stamp: 0x559f9ab4 Exception code: 0xc0000005 Fault offset: 0x0003609c Faulting process id: 0x1440 Faulting application start time: 0x01d76c3b875933ab Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FSX\ai_player.dll Report Id: 93d5bf09-8273-45bf-b5d9-7c1fe53d2c8e Faulting package full name: Faulting package-relative application ID: The above entry was for 00:34:09 There's another entry for 00:34:18 Faulting application name: vPilot.exe, version: 2.8.1.0, time stamp: 0x6022ee01 Faulting module name: ntdll.dll, version: 10.0.19041.1023, time stamp: 0xf739c3a5 Exception code: 0xc000000d Fault offset: 0x00104a34 Faulting process id: 0x4974 Faulting application start time: 0x01d76c3cf115cccd Faulting application path: C:\Users\91790\AppData\Local\vPilot\vPilot.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: b9686330-d7a2-4b84-92c3-216fd16a0a33 Faulting package full name: Faulting package-relative application ID: This may be due to vPilot detecting FSX CTD. vPilot had given me an error saying FSX crashed. Hope this ai_player.dll is enough information. I have no idea what this module is. Hope you can help. Thank you.
|
|
|
Post by aerofoto - HJG Admin on Jun 29, 2021 3:28:46 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
|
|
|
Post by Nathan Ford - HJG on Jun 29, 2021 5:33:53 GMT
I ran a couple of tests today and got the ai_player.dll in one of them and FSUIPC in the other. It has all of the tell tail marks of the uiautomationcore.dll problem rearing it’s ugly head again.
I have a download a different uiautomationcore.dll that was suggested on the “Steam” forums and it is being checked by Norton to make sure no one has buggered around with it, but that can take up to 48hrs. If it gets the all clear I’ll run some tests with that and see if it makes any difference. If that fixes it, I will send you a message here through the forum with a Dropbox link to get it and instructions on what to do.
Unfortunately, FSX and FSX-SE where designed for Win 7 and when Win 10 came out, the uiautomationcore.dll that came packaged with it was different and would cause FSX to CTD when changing views or accessing the menus. It was discovered that putting the original Win7 uiautomationcore.dll into the FSX route directory would fix this and FSX-SE came with the .dll already installed. I would say that one of the Windows 10 updates a couple of weeks ago has overridden this fix.
You guessed correctly, the vPilot error is from FSX no longer running.
Fingers crossed that the other uiautomationcore.dll works. I wouldn’t recommend downloading one off the net without having it checked first as people bugger around with them to get access to your computer.
Will keep everyone updated,
Nathan
|
|