Modified FTR.

Capricorne · Post by **Capricorne** » Thu Jun 20, 2019 6:08 pm

Hi René,
I think you didn't understand Thierry's answer correctly, because the answer he gave me is different : it's a problem in the scenery, not in server !:
That is what he say to me:
"You have to check with the designer of the scene. There is an altitude difference problem at the airport that causes the cheat control system to think that there is a notch because the glider starts higher (>150m) than the expected altitude."

BOD1 · Post by **BOD1** » Thu Jun 20, 2019 6:16 pm

Ok, I'll have a closer look tonight.

BOD1 · Post by **BOD1** » Thu Jun 20, 2019 7:03 pm

Someone has a FTR not accepted to provide?

BOD1 · Post by **BOD1** » Thu Jun 20, 2019 7:21 pm

Previous problem is not related to yours, Capricorne. yours is the problem I described in my PM, difference in altitude on Bebedouro airport: 585.9098 in FTR, for 551 reported.

Capricorne · Post by **Capricorne** » Thu Jun 20, 2019 9:15 pm

Here is my last ftr , start at Bebedouro in scenery of same name :http://www.nakaminow.info/CondorV2/bebeLast.ftr
and here the message from CC

Capricorne · Post by **Capricorne** » Fri Jun 21, 2019 2:58 pm

I give up....

Rene Queiroz · Post by **Rene Queiroz** » Sat Jun 22, 2019 2:17 am

Sorry, my friends, I'm going to check every detail of the scenery and make the necessary corrections!

Rene Queiroz · Post by **Rene Queiroz** » Sat Jun 22, 2019 2:37 am

Checking now, there is no altitude difference in the original file!

Rene Queiroz · Post by **Rene Queiroz** » Sat Jun 22, 2019 2:35 pm

Friends, I tried to do the same Capricorne flight, and the problem appeared ... But in our previous flights none of this happened ... I'm not sure how to solve this bug ... I ask for help!

BOD1 · Post by **BOD1** » Sat Jun 22, 2019 2:53 pm

On flight planner, terrain height is 551 meters. Right click on airport indicates also 551 meters
But on Terrain Editor, airport altitude property indicates 585m and terrain height is also 585 meters.
So, I'm stuck too.

Oxo?

Rene Queiroz · Post by **Rene Queiroz** » Sat Jun 22, 2019 4:11 pm

If I modify the altitude from the airport to 551meters in Landscape Editor? Maybe it would solve the problem? And new Patch would be released.

EDB · Post by **EDB** » Sat Jun 22, 2019 5:21 pm

Calibration in this Bebedouro2 landscape is off by at least 3,5km in the Fronteira area... Because of this the altitudes around the Bebedouro airport are also way off.

The airport lays at 592m in real life. In this landscape it lays between 565-434-582m (551m at the center of the runway). The landscape builder flattened at 585m. And the main problem now is that the landscape builder didn't do a TRN from TR3 action. That action isn't there for the show...

Other landscapes that can have these problems (status end of 2018) :
CW-A Alps 1.1 (Dec. 27th, 2018)
Netherlands HD (Dec. 6th, 2018)
Cascade Range (May 21st, 2018)
CW-V Vysocina (Feb. 20th, 2018)
Denmark 5 for Condor 2 (May 7th, 2018)
Lake Keepit C2 (Aug. 11th, 2018)
New Zealand (Condor 2) (Nov. 30th, 2018)
Arizona 2 (July 13th, 2018)
Jura Mont-Blanc 2 v2 (May 21st, 2018)
Maroc Haut Atlas (Dec. 14th, 2018)
France Sud C2 (Nov. 24th, 2018)
Corse C2 (Nov. 6th, 2018)
Netherlands (Nov. 8th, 2018)
Scotland 3 (Feb. 27th, 2018)
Bebedouro 2 (July 13th, 2018)
Chypre (March 24th, 2018)
Provence 18 (Oct. 31st, 2018)

PS
Bebedouro 2 (July 13th, 2018) also has other status issues/non-Condor2 standards.
No forrestmaps
24-bit GUI map
RealtimeShading=0
No thermalmap

I have some idea why calibration is way off...

2019-06-22 17_58_53-Condor Landscape Toolkit 2_ Landscape Editor.jpg

Capricorne · Post by **Capricorne** » Sat Jun 22, 2019 6:08 pm

Rene Queiroz wrote: ↑
Sat Jun 22, 2019 2:35 pm
Friends, I tried to do the same Capricorne flight, and the problem appeared ... But in our previous flights none of this happened ... I'm not sure how to solve this bug ... I ask for help!

You don't need to do the same flight as the one I have posted. I have try "winch launch" ,"Airborne"or "Aerotow" in FREE FLIGHT mode and MULTIPLAYER....! in all mode the start altitude seem to be ok:
Only in XCSoar I have strange value:

XCSoar main screen:

altitude is baro= 586m, but no idea with the red -6m ? and value for Bebedouro GLD flugplatz are also different

Have also no idea why we see 551m in in "FLIGHT PLANNER"...

Rene : have you post in the past one flight (ftr) on CondorClub that I could download?

dgtfer · Post by **dgtfer** » Sat Jun 22, 2019 7:56 pm

Calibration errors cannot be the cause of this problem, even if it may cause an error with XCsoar. The difference between XCsoar and Condor may also come from a difference between the relief model used by XC and the condor model (tr3 files), but however, that's not the present problem.
But the difference between Condor and it's flight planner can actually come from the difference between the tr3 and the trn file, which is, among other things, used by the flight planner. Besides the present problem, it may cause various other ones.
If this is the case, it is simple for Rene to generate a new trn file with Landscape editor and everything should be fine.

Rene Queiroz · Post by **Rene Queiroz** » Sat Jun 22, 2019 8:36 pm

... it is simple for Rene to generate a new trn file with Landscape editor and everything should be fine.
As proposed by Dgfter, I made the necessary changes and am sending a compressed file to CondorClub.
Thanks for the precious help!
Thank you all!

Modified FTR.

Re: Modified FTR.

Re: Modified FTR.

Re: Modified FTR.

Re: Modified FTR.

Re: Modified FTR.

Re: Modified FTR.

Re: Modified FTR.

Re: Modified FTR.

Re: Modified FTR.

Re: Modified FTR.

Re: Modified FTR.

Re: Modified FTR.

Re: Modified FTR.

Re: Modified FTR.

Re: Modified FTR.