#744 Automatic Scenery Download: Failed to synchronize directory... error code= 256

[Anonymous]

Originally created by: ramiromi... (code.google.com)@gmail.com

*What steps will reproduce the problem?*
1. Start fgfs
2. Select Airport From List (TNCM)
3.

*What is the expected output? What do you see instead?*
The Automatic Scenery Download save the data to selected Target Directory but there are some problems with the URLs with some Scenery

*Any output in the console (black window)?*
fgfs
Starting automatic scenery download/synchronization. Using external SVN utility 'svn'. Directory: '/home/ramiro/FlightGear/Escenarios'.
KI266 dme indicator #0 initialized
loading scenario 'nimitz_demo'
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib audio/pcm_bluetooth.c:1613:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1613:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1613:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1613:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
creating 3D noise texture... DONE
weather util initialized ...
Initializing Nasal Electrical System
power up
passed invalid index (0) to FGRouteMgr::jumpToIndex
svn: El URL «http://terrascenery.googlecode.com/svn/trunk/data/Scenery/Objects/w070n10/w063n18» no existe
Failed to synchronize directory 'Objects/w070n10/w063n18', error code= 256
svn: El URL «http://terrascenery.googlecode.com/svn/trunk/data/Scenery/Objects/w070n10/w062n18» no existe
Failed to synchronize directory 'Objects/w070n10/w062n18', error code= 256
svn: El URL «http://terrascenery.googlecode.com/svn/trunk/data/Scenery/Terrain/w070n10/w062n18» no existe
Failed to synchronize directory 'Terrain/w070n10/w062n18', error code= 256
svn: El URL «http://terrascenery.googlecode.com/svn/trunk/data/Scenery/Objects/w070n10/w062n19» no existe
Failed to synchronize directory 'Objects/w070n10/w062n19', error code= 256
svn: El URL «http://terrascenery.googlecode.com/svn/trunk/data/Scenery/Terrain/w070n10/w062n19» no existe
Failed to synchronize directory 'Terrain/w070n10/w062n19', error code= 256

*What FlightGear version are you using (when using GIT version, please
mention date)?*
2.6.0.1 from PlayDeb.net

*What operating system and graphics card?*
Ubuntu 11.10
Nvidia GTS 250

*Please provide any additional information below or as attachment (Avoid
expiring external links, such as to imageshack/pastebin/...).*

This happen with a lot of Airports from the list.

Enviroment variables:
FG_ROOT=/usr/share/games/flightgear
FG_SCENERY=/usr/share/games/flightgear/Scenery:/home/ramiro/FlightGear/Escenarios

[Anonymous]

Originally posted by: bre... (code.google.com)@gmail.com

Happens for every scenery area covered by ocean, since the scenery server does not contain any data for ocean areas. Unfortunately, FG doesn't know in advance whether an area is ocean or land. So, it has to try and download anyway - so download errors are expected for ocean tiles. And then it's not really possible to tell whether the download failed, since scenery is intentionally missing (= ocean), or whether scenery is missing due to an error.
So, you can ignore these messages for now.

In the long term, it would be nice if we could explicitly identify ocean areas, i.e. by creating empty directories on the scenery server for such tiles, or by providing a "black list" of scenery areas, known to be ocean - so we can tell the difference.

Status: Stalled

[Anonymous]

Originally posted by: bre... (code.google.com)@gmail.com

Had a closer look: indeed, the "ocean issue" is already covered - such errors are ignored. However, this requires detailed error handling - which only works when using the libsvn library. The above binary was built without "subversion" support - so it uses a fallback to use an external "svn" utility. The external utility doesn't provide any detailed error reports (fgfs doesn't know whether the download failed, since there simply is no scenery, or whether there was a genuine download issue).

So, please contact the guys maintaining "PlayDeb.net" (or whoever built the binary) and tell them "Please rebuild the SimGear library with libsvn/libapr libraries installed.".

This will improve the scenery download feature a lot. It's not possible to improve the support for the external SVN support (when using the fallback external "svn" utility).

Status: WontFix

[Anonymous]

Originally posted by: ramiromi... (code.google.com)@gmail.com

Ok, I see. Thank you. Reported in PlayDeb.net launchpad.

[Anonymous]

Originally posted by: bre... (code.google.com)@gmail.com

More Linux/BSD distros provide FlightGear/SimGear packages which were compiled without libsvn support, though (almost) all distros should have svn libraries.

Currently, we're almost silently ignoring the issue, disable the libsvn feature and use the fallback - so few (package) builders ever notice they could improve.

I'm going to change the cmake files, so that a missing libsvn dependency is treated as an error, if "ENABLE_LIBSVN" is "ON" (at least for the non-MSVC platforms) - this should raise awareness ;-). However, I'll only do that after the current release (>= 2.9.0).

[Anonymous]

Originally posted by: ramiromi... (code.google.com)@gmail.com

Playdeb.net just published a new package for FlightGear with the fix. I'm gonna try it.