Neto constant sink and .exe error

[Ezepilot]

Hello to all the condor team.
I need to consult because I am having two problems, specifically and more often in the Argentine task, with Argentine scenarios.
The problem is that my neto vario is almost constant in -0.4 -0.3 -0.5 ...
The lanscape is absolute flat so no chance about wave ... and if i try for example fly away from cluds for avoid downdraft from clouds the vario is still in negative about kilometers and kilometers ....(my joystick is centered)
I know that sometimes it happens that the vario mark down but it seems really strange that this happens perhaps for 10 kilometers or more ... it seems that the glider is constantly in a descending air mass ...
I am also having condor.exe errors that I am going to leave the capture of the photo and some video so that they see the negative in the vario ...
I have some time flying in condor and this never happened to me ... especially in European landscapes and tasks where I have never had problems ...
I can add to all this that in the Argentine scenarios like Buenos Aires there is a difference between the Cotasa and XCSOAR wind marking.
For example the correct reading of the wind is in the xc while in the cotasa it marks the wrong wind direction ...(only in argentinian servers) if i refly and host same task on my own... i have no problems with wind indicators or sink...strange uh?
I hope you can give me help since I don't know what it can be ... besides all these problems only happen to me in Argentine scenarios and not in Europe.
It's really strange ... I don't know what to think ...because it happens only in Argentine servers, specifically on quarantine argentine cup....
Not have problems or exe problems never in tchin tchin or another european competitions.
Thank you very much for the time to read me and I hope you can help me...
Pd..sorry about bad quality of video and photo. I Paste my log too...and in condor 2 logs i have Hundred of files that said...RegKeyDuplicate_(numbers).txt is normal? Video below.

Code: Select all

CONDOR LOG STARTED AT 19:34:14
Condor version: 2110
Creating splash screen.
Loading cursors.
Loading fonts.
Creating controlers.
Creating client.
Creating replay.
Creating flighttrack.
Loading GUI skins.
Loading skin hash list.
Checking skin hash list.
Saving skin hash list.
Reading language.
Writing installdir.
Reading lastplayer.
Reading defaultlandscape.
Loading Setup.
Destroying splash screen.

ENTERING FLIGHTPLANNER.

STARTING MULTIPLAYER (CLIENT) SIMULATION AT 19:36:43.
Debug mode: False, False.
Creating window.
0: NVIDIA GeForce GTX 1050 Ti.
VIDEO RAM: 3072.0 Mb.
1: Microsoft Basic Render Driver.
VIDEO RAM: 0.0 Mb.
SELECTED: NVIDIA GeForce GTX 1050 Ti.
VIDEO RAM: 3072.0 Mb.
Monitor: \\.\DISPLAY1.
Left: 0.
Right: 1920.
Top: 0.
Bottom: 1080.
Attached to desktop: True.
Initializing DirectX 11 framework.
Window size: 1920 x 1080.
Created D3D11 Device.
Created Swap Chain.
Created RenderTarget View.
Created DepthStencil Texture.
Created DepthStencil View.
Created DepthStencil ShaderResourceView.
Created 1 swap chains.
Finished initializing DirectX 11.
Creating game objects.
Aquiring controlers.
Force feedback not initialized.
Initializing TrackIR.
Init_TrackIR_Dll failed with error code: 4.
TrackIR initialization failed.
Creating Scene.
Creating HUD.
Creating Sound.
Loading sounds.
Creating Flightcomp.
Loading polar data.
Creating UDP.
Loading turnpoints.
Creating home airfield.
Creating Ghosts.
Creating Avion.
Creating Cameras.
Creating World.
Creating Land.
NetPlayer disconnected: Serverlist crawler.
Creating Ground objects.
Creating Sun.
Creating Sky.
Creating Wind.
Creating Thermals.
Creating High Clouds.
Creating Middle Clouds.
Creating Turbulence.
Creating CloudFog.
Creating LiftHelp.
Creating TaskHelpers.
Creating Airports.
Creating CloudShadows.
Initializing Sun.
Initializing Airports.
Computing coarseHeightMap.
Caching terrain.
Tesselating Land.
TaskHelpers AfterTesselate.
Airports AfterTesselate.
Initializing Thermals.
HighClouds AfterRefresh.
Initializing middle clouds.
Initializing cloud shadows.
Initializing Avion.
Loading Avion.PlaneData from Ventus3-18.
Creating Avion.Water.
Creating Avion.Wheelsmoke.
Creating Avion.Smoke.
Creating Avion.GeometryIE.
Creating Avion.GeometryS.
Creating Avion.Skin.
Creating Avion.PolarData.
Creating Avion.FusPolarData.
Creating Avion.Stress.
Creating Avion.Damage.
Creating Avion.Flex.
Creating Avion.RCN.
Creating Avion.Panel.
Creating Avion.Pilot.
Preparing for start.
Initializing Cameras.
Initializing FlightTrack.
Initializing FlightComp.
Creating NMEA.
Initializing GroundObjects.
Loading Network Players.
Requesting start slot....
Initializing timer.

ENTERED SIMULATION AT 19:36:56.
NetPlayer connected: Serverlist crawler.
NetPlayer disconnected: Serverlist crawler.
Landscape refresh start at 19:41:40.
Landscape refresh stopped at 19:41:46.
Landscape refresh start at 19:47:20.
NetPlayer disconnected: R.Morales.
Landscape refresh stopped at 19:47:25.
NetPlayer disconnected: J.PH.
Landscape refresh start at 19:59:51.
Landscape refresh stopped at 19:59:55.
Landscape refresh start at 20:02:12.
Landscape refresh stopped at 20:02:17.
Landscape refresh start at 20:04:54.
Landscape refresh stopped at 20:04:59.
Landscape refresh start at 20:07:30.
Landscape refresh stopped at 20:07:36.
Landscape refresh start at 20:10:16.
Landscape refresh stopped at 20:10:21.
Landscape refresh start at 20:12:47.
Landscape refresh stopped at 20:12:52.
NetPlayer disconnected: A.Palomba.
Landscape refresh start at 20:20:18.
Landscape refresh stopped at 20:20:24.
NetPlayer disconnected: S.Bollatti.
Landscape refresh start at 20:25:27.
Landscape refresh stopped at 20:25:32.
Landscape refresh start at 20:27:10.
Landscape refresh stopped at 20:27:15.
Landscape refresh start at 20:28:11.
Landscape refresh stopped at 20:28:16.
Landscape refresh start at 20:28:56.
Landscape refresh stopped at 20:29:01.
NetPlayer disconnected: P.Drazul.
Landscape refresh start at 20:35:30.
Landscape refresh stopped at 20:35:36.
Landscape refresh start at 20:40:08.
Landscape refresh stopped at 20:40:13.
NetPlayer disconnected: O.Trivellini.
Landscape refresh start at 20:41:37.
Landscape refresh stopped at 20:41:43.
Landscape refresh start at 20:43:30.
Landscape refresh stopped at 20:43:35.
Landscape refresh start at 20:44:37.
Landscape refresh stopped at 20:44:42.
Landscape refresh start at 20:45:12.
Landscape refresh stopped at 20:45:17.
Landscape refresh start at 20:50:26.
Landscape refresh stopped at 20:50:31.
Landscape refresh start at 20:51:30.
Landscape refresh stopped at 20:51:35.
Landscape refresh start at 20:52:17.
Landscape refresh stopped at 20:52:23.
Landscape refresh start at 20:54:07.
Landscape refresh stopped at 20:54:14.
Landscape refresh start at 20:56:03.
Landscape refresh stopped at 20:56:09.
Landscape refresh start at 20:58:55.
Landscape refresh stopped at 20:58:59.
Landscape refresh start at 21:00:37.
Landscape refresh stopped at 21:00:41.
Landscape refresh start at 21:02:27.
Landscape refresh stopped at 21:02:32.
NetPlayer disconnected: j.baccola.
Landscape refresh start at 21:04:31.
Landscape refresh stopped at 21:04:36.
Landscape refresh start at 21:06:26.
Landscape refresh stopped at 21:06:31.
Landscape refresh start at 21:15:36.
Landscape refresh stopped at 21:15:41.
Landscape refresh start at 21:17:19.
Landscape refresh stopped at 21:17:24.
Landscape refresh start at 21:19:02.
Landscape refresh stopped at 21:19:07.
Landscape refresh start at 21:20:49.
Landscape refresh stopped at 21:20:54.
Landscape refresh start at 21:22:38.
Landscape refresh stopped at 21:22:43.
Landscape refresh start at 21:24:24.
Landscape refresh stopped at 21:24:29.
NetPlayer disconnected: W.BUSCARONS.
NetPlayer disconnected: C.Allende.
Landscape refresh start at 21:31:57.
Landscape refresh stopped at 21:32:02.
Landscape refresh start at 21:33:53.
Landscape refresh stopped at 21:33:58.
Landscape refresh start at 21:36:06.
Landscape refresh stopped at 21:36:10.
NetPlayer disconnected: J.Mascheroni.
NetPlayer disconnected: M.Aversa.
Landscape refresh start at 21:45:16.
Read magic value,  at 21:45:18: Access violation at address 0040A385 in module 'Condor.exe'. Write of address 00000001.

https://youtu.be/zfOpeSB5LgE

[Bre901]

I can add to all this that in the Argentine scenarios like Buenos Aires there is a difference between the Cotasa and XCSOAR wind marking.
For example the correct reading of the wind is in the xc while in the cotasa it marks the wrong wind direction

CoTASA displays a constant wind indication (data from the .fpl file) whereas XCSoar computes it on the fly

Have you tested the netto with no wind and no thermals ?

Besides that, when you post the contents of a file, please use the code tags : "</>" in the toolbar

[EDB]

You must do that test at thermalling speed. Not 150k.
And in still air (edit the .fpl to set all weather settings at zero) on a flat surface.

[Ezepilot]

I can add to all this that in the Argentine scenarios like Buenos Aires there is a difference between the Cotasa and XCSOAR wind marking.
For example the correct reading of the wind is in the xc while in the cotasa it marks the wrong wind direction

CoTASA displays a constant wind indication (data from the .fpl file) whereas XCSoar computes it on the fly

Have you tested the netto with no wind and no thermals ?

Besides that, when you post the contents of a file, please use the code tags : "</>" in the toolbar

The readings of wind are completely different specifically on that server. Not in another servers, in another servers work perfect, both work good.
For example, in that server if i have true north wind on condor my xc show corrects display of wind but the cotasa show for example east wind direction.
And the neto problem seems specifically on this server too...
I try same task hosting myself and i dont have that constant sink... i try of course with settings no thermals no wind ...and not happen...
It seems it only happens when i conect to this server.
Another problem was the .exe error that never happens before on my condor.
Sorry about the Code tags I don't usually use the forum practically and I didn't know it.
I already corrected it.
Greetings.

[Bre901]

I hadn't looked at the video, have you compared the netto indication in CoTASA with the one seen on the e-vario when in sped-to-fly mode ?

The values you show are actually not that big.

What glider were you using ? how much ballast ?

Could you please indicate the server that has problems and post a flight plan so that we can also do some tests

[Ezepilot]

I hadn't looked at the video, have you compared the netto indication in CoTASA with the one seen on the e-vario when in sped-to-fly mode ?

The values you show are actually not that big.

What glider were you using ? how much ballast ?

Could you please indicate the server that has problems and post a flight plan so that we can also do some tests

Yes no problem!. Yes, i was comparing the Cotasa values and change it on my E Vario and it seems correct, because i have the same sink on both...
I know it`s not that big values but when extends about 15 or 20 kilometers really is a destructive glide ratio..
For example on my final glide (it seems sink enlarge on final glide) real crazy...but it happens... i have +150 m on ddh and i have consistant -0.5 all the time maybe for 10 kilometers or more that kill my glide, despite trying to get away from the downdraft of the clouds (... It doesn't happen to me on other servers or other tasks, it really is very strange...
Of course i check my airbrakes are closed, and seems my joystick is correctly calibrated. I check twice or more with the turn cordinator and the glider doesn´t slide. so its ok.
The glider i was using was the ventus 3 18M (my favourite) with full water and CG -1, But 1st May i fly with the Genesis and happens the same, and same with the LS4 the 30 april. all tasks in Buenos aires and Pehuajo. (completely flat land)
I can gladly send the flight plan and indicate on which server it happens to me.
I attach the file here.
The server is https://www.condor-club.eu/comp/show/0/?id=391 I fly on the hour 22:15 UTC Because ar two different schedules.
Honestly i dont have any idea what could be, because it doesn't happen on other servers.
Thanks for read me and for your time.

[Ezepilot]

hello condor team, I know you are always very busy with the condor but I really need help with this.
I have recorded a new video where in one minute you can see the net vario at -0.5.
Today I started the test with the normal vario the neto had normal readings, then it sank more and more ... between -03 and -0.4 later in final glide as it is always the worst part and the descending is nailed to -0.5 .. .
Of course this is annihilating my planes and finally I can't fly this way, that's why I turn to your help ...
I have noticed that after losing my ddh +180final glide in a few kilometers for the neto in negative.
A no less important fact is that when a specific participant disconnected, my neto vario returned to normal with 2 kilometers to finish.
Also attached another video where you can see the difference in the wind between the cotasa and the xcsoar.
I'm sorry to have to resort again but I have no way of solving it but with your help.
Greetings and thanks for taking the time to read me
Neto negative For kilometers
https://www.youtube.com/watch?v=uC_v8lJ1-Vw

Inconsistant wind between cotasa and xc soar
https://www.youtube.com/watch?v=ziEpOsudTb4

Could be scenery problem? today two guys test it and maybe same problem as me.

[Bre901]

Inconsistant wind between cotasa and xc soar
https://www.youtube.com/watch?v=ziEpOsudTb4

I already mentioned above that the wind in CoTASA is just the wind as it is defined in the FPL
The wind in XCSoar can only be computed when you make turns (min 180°), as there is no speed and heading information in the NMEA data sent by Condor.
The estimation is not precise until you have made a few complete turns.
It is not re-evaluated when you fly a straight line, which means that it is not always up-to-date
If you want a real-time indication of the wind you must look at the PDA screen 4 (hit the corresponding key twice - default=4)

Could be scenery problem? today two guys test it and maybe same problem as me.

I really don't see how it could be a server problem, everything is computed locally (if you loose the Internet connection during an online flight you are able to continue flying), so it must be indeed a landscape or task problem.
Have you tried flying the same task offline ? (use the flight recordings as ghosts and enable the miracle key so that you can make sure you are at the problematic place at the same time as the ghost gliders)

Please post the FPL of the last flight

[Angry Ivy]

Hi!
Is there any chance you found out what the problem was? I think I have experienced this same issue myself.

Constant netto of -0.5, and had to re-climb onto final glide multiple times over flat landscape, and even after that, I almost didn’t make it. The plane keeps sinking below path, flaps/gear/airbrakes all in the right configuration. The sink its not extreme, but over the long glide it makes for a pretty substantial difference! Almost landed out because of it.

I think I have seen enough flights in condor to believe something was out of the ordinary.

Would love to hear if you have any more info.

Thies

[Bre901]

Would love to hear if you have any more info.

Almost 6 months ago I asked this :

Have you tried flying the same task offline ? (use the flight recordings as ghosts and enable the miracle key so that you can make sure you are at the problematic place at the same time as the ghost gliders)

Please post the FPL of the last flight

... and got no answer

How do you guys expect to have answers to your questions if you don't provide any information on how to reproduce your issues ?

We need to have access to an FTR where the problem has been identified so that we can investigate.

[Angry Ivy]

Sorry to hear you didn’t find the solution yet.

I have had this problem a long time ago, but never really investigated it then.

Yesterday I had it again. Some info:
- The landscape was AA (I noticed it over a flat part of the scenery)
- I was hosting the dedicated server myself
- Not sure if it is related, but I got disconnected from my own server (the image froze for around 20-30 seconds, and suddenly I was flying offline).
- Only after I got disconnected from multiplayer, I started to notice the problem. However, I am not exactly sure when it began, so this could be non-related.
- Other pilots flying online at roughly the same position, didn’t seem to have the same problem.
- The problem seemed to be occurring for at least the last 80km final glide, constantly. Possibly longer, but I only started to notice it once I was over flat terrain, being busy with my arrival height (ddh).

[wickid]

Flightplan please so we can try to reproduce!

[Angry Ivy]

1000km.fpl

The problem could also be the speed to fly command (in combination with the constant negative netto value).

I mean this in a way that the planes' performance is not affected, but that the speed to fly command gives the instruction to fly faster than might be suitable in the situation (maybe because of the netto sink the instrument displays), and therefore you might have the poor gliding ratio matching with that higher speed.

The only actual info that I have is:
- Constant -0.5 displayed on netto vario
- If you accurately follow the speed-to-fly as instructed, you won't make it to the airport.

[Bre901]

1000km.fpl

Ouch !

IIRC, you mentioned you still had an IGC file (can't find it anymore), there is an IGC -> FTR converter on Condor-Club, could you please try it

Let's hope the guys that had that problem previously have shorter tasks

- Constant -0.5 displayed on netto vario
- If you accurately follow the speed-to-fly as instructed, you won't make it to the airport.

It makes sense, if you were on the glide slope without any safety margin and either encounter sink or start flying too fast because of incorrect netto value, this is not surprising

[Angry Ivy]

Haha yes, it was a bit of a long one.

I flew the last 50km again with my ghost. It is not so easy to compare, as the weather is randomized each flight, and the previous me was flying through quite a few thermals along the way .

By just following it, and matching the speed (so not aiming for thermals in the weather I am flying in), I was able to only gain 100m and finish around 3km ahead. So I guess performance wise, this difference is so small that I would say it could be just the weather difference.

However, I did notice that the ghost was flying quite a bit faster than what I would normally do with that MCready setting (except for the last bit where I was descending below the path and therefore started reducing speed to squeeze the glide a bit further ).
As I pretty much follow speed to fly on the flats, and used the same MC setting both flights, it still feels like the first flight got different speed to fly instructions. Also, the second flight, my netto vario was varying around +-0.0 like I would normally expect, different than the constant -0.5 like I had the first time.