Can I download FSUIPV6 prior version?

[shibekora]

Hi 

I have been using FSUIPC very conveniently for log time thank you.

Now I have FSUIPC6 for p3dV6.1.11 registered.   FSUIPC version is as follows by log file

********* FSUIPC6, Version 6.2.1 (19th July 2024) by Pete & John Dowson *********
Prepar3D.exe version = 6.1.11.31619
Running inside Prepar3D v6
Module base=7FFEB5760000
Windows 10 Home 64 Bit reported as Build 22631, Release ID: 2009 (OS 10.0)
Reading options from "C:\Users\shibe\Documents\Prepar3D v6 Add-ons\FSUIPC\FSUIPC6.ini"
Checking the Registrations now ...

Recently I have a strange issue that CTD happens exactly same indicated altitude at 2700ft with fair weather condition by any type of aircraft and wherever of airport. The altitude is just below 3000ft from the lower altitude of cloud layer.

If I set more higher altitude for its layer like 1000ft more, the CTD altitude become higher by exactly same of 1000ft.     It is not related to the type of cloud.  P3d default altitude for fair weather is 5730ft, CTD happens at 2700ft.

So far, I have made clean uninstall and install p3d, and made flight without any add-ons except FSUIPC, Spad.next and chaseplane pro. 

However I have CTD at the same altitude.

Today, finally I have made flight with deleteing FSUIPC6 from P3dv6 add-ons folder, no CTD at 2700ft and above.

I have updated FSUIPC6 from 6.2 to 6.2.1  in this summer when I had different issue with activesky.  Support from HIFI, FSUIPC might have some unmatch trouble with activesky v6,  therefore I should update to new one.    It seems CTD at 2700ft have started at that period. 

To my regret I do not have back up of prior version6.2 and no link for prior version in the Pete & John Dowson's software web site.

That is why I made this inquiry.  

Could you please give me a opportunity to try with prior version?

shibekora

[John Dowson]

10 hours ago, shibekora said:

I have updated FSUIPC6 from 6.2 to 6.2.1  in this summer when I had different issue with activesky.  Support from HIFI, FSUIPC might have some unmatch trouble with activesky v6,  therefore I should update to new one.    It seems CTD at 2700ft have started at that period. 

Are you using the correct Active Sky dll (as_connect.dll) for the version you are using? Please check that first.
Otherwise, weather CTDs are normally caused by a corrupt *.wx fille, so please check this - see 

If you still get crashes, please show me your FSUIPC6.log fo;e, as well as any crash reports for this in the Windows Event Viewer.

10 hours ago, shibekora said:

I have updated FSUIPC6 from 6.2 to 6.2.1  in this summer when I had different issue with activesky.  Support from HIFI, FSUIPC might have some unmatch trouble with activesky v6,  therefore I should update to new one.    It seems CTD at 2700ft have started at that period. 

Again, check that you are using the latest version of AS6 and have the correct AS dll installed (if using).

10 hours ago, shibekora said:

To my regret I do not have back up of prior version6.2 and no link for prior version in the Pete & John Dowson's software web site.

I do not provide old and unsupported versions - I only move foreword. I doubt very much this has anything to do with the change from 6.2.0 to 6.2.1, but I have attached the 6.2.0 dll below for you to confirm.

John

FSUIPC6.dll

[shibekora]

Thank you John

I have tried flight with ver6.2, however I got same CTD at 2700ft.

So, my issue is not related to the version.  I am sorry for bothering you on my issue.

I have to research what is the cause by other way including Pete's topic referred by you.   

Anyway, thank you again.

PS.

Now I am trying to find the cause without activesky, so CTD now talking has no relation with activesky.

Shibekora 

FSUIPC6_v62_CTD.log

[John Dowson]

11 hours ago, shibekora said:

So, my issue is not related to the version.  I am sorry for bothering you on my issue.

Yes - there weren'r that many updates between these versions, and nothing that could cause a CTD.

The log file you attached ends after 80 seconds - so did P3D crash on start-up? Of so, that is usually a sign of a corrupt weather file. 

Try setting "NoWeatherAtAll=Yes" in the [General] section of the FSUIPC6.INI file to disable weather - if that fixes it, then you have a corrupt weather file which needs to be removed (see that FAQ entry I referenced).

If thats not it, check the Windows Event viewer to see where the crash occurred, and maybe check the P3D forums for similar CTD reports.