Condor Update 2.1.2

Moderator: BOD1

Post Reply
evergreen
Posts: 7
Joined: Sat Apr 25, 2020 4:20 am

Condor Update 2.1.2

Post by evergreen » Sat May 09, 2020 12:54 am

Hi,

I just installed Condor update 2.1.2 as well as hangar update 14.

When I click on start flight I get the following message: Access violation at address 00490884 in module "Condor.exe". Read of address 027DFFF8.

Help!

Thanks for your help.

Steve

User avatar
Yhuki Nagasaki
Posts: 3
Joined: Sun Feb 04, 2018 5:20 am

Re: Condor Update 2.1.2

Post by Yhuki Nagasaki » Sat May 09, 2020 8:03 am

Hi !
Me too. :(
after installed "CondorPatch212" and "HangarUpdate14".
error message below

same problem?

thanks for your help!

Yhuki
You do not have the required permissions to view the files attached to this post.
Last edited by Yhuki Nagasaki on Sat May 09, 2020 8:09 am, edited 1 time in total.

User avatar
wickid
Posts: 2442
Joined: Mon Dec 04, 2006 7:32 pm
Location: Venlo, NL
Contact:

Re: Condor Update 2.1.2

Post by wickid » Sat May 09, 2020 8:09 am

Delete or rename the condor folder in my documents. Restart Condor and recreate your pilot.
Last edited by wickid on Sat May 09, 2020 8:20 am, edited 1 time in total.
PH-1504, KOE

User avatar
Bre901
Posts: 1799
Joined: Tue Nov 22, 2016 8:57 pm
Location: Annecy (France)
Contact:

Re: Condor Update 2.1.2

Post by Bre901 » Sat May 09, 2020 8:20 am

wickid wrote:
Sat May 09, 2020 8:09 am
Delete the condor folder in my documents. Restart Condor and recreate your pilot.
If you want to save your flightplans, flighttracks, settings, logbook, etc, make a backup copy of that folder before deleting it.
CN: MPT — CondorUTill webpage: https://condorutill.fr/

User avatar
Bre901
Posts: 1799
Joined: Tue Nov 22, 2016 8:57 pm
Location: Annecy (France)
Contact:

Re: Condor Update 2.1.2

Post by Bre901 » Sat May 09, 2020 9:08 am

CN: MPT — CondorUTill webpage: https://condorutill.fr/

User avatar
Yhuki Nagasaki
Posts: 3
Joined: Sun Feb 04, 2018 5:20 am

Re: Condor Update 2.1.2

Post by Yhuki Nagasaki » Sat May 09, 2020 11:16 am

hi !

"Delete or rename the condor folder in my documents. Restart Condor and recreate your pilot."

It worked ,thanks.

"If you want to save your flightplans, flighttracks, settings, logbook, etc, make a backup copy of that folder before deleting it."

I backuped condor folder in my documents before delete.
Then copyed backuped files in troubled condor folder to new condor folder except pilot.ini file.
But same error again :(

I tryed "Delete or rename the condor folder in my documents. Restart Condor and recreate your pilot." again.
It worked, Condor2 run properly.
I backuped brand new logbook file for test.

Then copy only logbook file in trobled condor folder to new condor folder.
Same error again :( :(

I removed this logbook file and copyed new logbook file that I backuped one fot test.
Condor2 run properly?
NO same error again :?: :?: :?:
thanks for your help :D

hugoachoy
Posts: 3
Joined: Tue May 21, 2019 6:32 pm

Re: Condor Update 2.1.2

Post by hugoachoy » Sun May 10, 2020 5:16 am

The same thing happens to me and the proposed solutions work the first time, but then the problem returns. I have also tried uninstalling and deleting registry data, always with the same result. Official response ???

User avatar
wickid
Posts: 2442
Joined: Mon Dec 04, 2006 7:32 pm
Location: Venlo, NL
Contact:

Re: Condor Update 2.1.2

Post by wickid » Sun May 10, 2020 8:28 am

hugoachoy wrote:
Sun May 10, 2020 5:16 am
The same thing happens to me and the proposed solutions work the first time, but then the problem returns. I have also tried uninstalling and deleting registry data, always with the same result. Official response ???
Bug was identified and there will be a patch soon. In the mean time if you are planning to buy an additional plane that fixes it as well. Appears that it only happens when you have a default Condor with no additional planes. If not, then there will be a patch in the next week or so.
PH-1504, KOE

evergreen
Posts: 7
Joined: Sat Apr 25, 2020 4:20 am

Re: Condor Update 2.1.2

Post by evergreen » Sun May 10, 2020 5:37 pm

Update to version 2.1.3 and the problem is fixed.

Post Reply