Help!!! (L'Alpe d'Huez (LFHU))

[Guest HeliFLYer]

Hi, anyone of ROTW listening here?I installed L'Alpe d'Huez (LFHU) and verified that the POD/SCF File are installed correctly in the scenery folder.But the scenery is not showing correctly (see attached screenshots). Only a runway artefact and a lonly tree? can be seen.I did a second test and unpodded the scenery and copied it into the correct folders - no change!There must be a CONFLICT with another (French?) scenery I have installed, I think. Before searching for hours just the question - anything known about possible scenery conflicts at ROTW?Thank you in advanceGeorgHeliFLYER EDDWhttp://forums.avsim.net/user_files/104644.jpghttp://forums.avsim.net/user_files/104645.jpg

[Guest Steve Brown]

Georg!Just add water to make them grow :-lol Sorry mate I have no idea myself, had the same thing happen too.Steve[divalign=center]http://www.wrexhamspace.org/sig.jpg][/divMy Websitehttp://www.wrexhamspace.org

[Guest Fly II Pilot]

Georg,I get the same thing and I did install the SE SRTM elevations by Beralex...Here's what I did to fix it:- Unpod the Scenery.S01 file to the dataD004163- Edit the Scenery.S01 file with Notepad or Wordpad- Do a search and replace (CTRL H) and change 6128 with 6378 (i.e., add 250ft to the parts' elevation).- Save the Scenery.S01 fileDone!For some reason, it seems that there's about a 250ft difference, maybe this has something to do with the US vs. the International version...Let me know if it doesn't work.By the way, what a fantastic job!!!Regards,http://www.avsim.com/hangar/fly/dfdg/banneraa.jpg

[Guest HeliFLYer]

Hi Alejandro,first of all thank you for your immediate help and instructions which allowed me to correct the problem to some extend.The scenery shows up and FLY!ing to LFHU and landing is no problem.But if I select LFHU in the menu then I find the aircraft on the ground UNDER the scenery, trying to move the plane crashes it (thats correct, gets in contact with objects of the scenery) and the "repair" function puts the aircraft in the air high above the airfield.Two other phenomenons are that 1. FLY! pauses for many seconds when I change to the outside views and I get to the tower view and 2. FLY! slows down more and more when FLY!ing over the scenery, at last I get 1 two 2 frames per second.I have not to work and cannot do further investigation, but this very late evening I'll try it without the France SE elevation POD, maybe I get better results then.Once again, thank you very much Alejandro! And I agree, the scenery itself is fantastic and it is crazy to land with a slight positiv vario!Thank you ROTW!RegardsGeorg HeliFLYer EDDWhttp://forums.avsim.net/user_files/104765.jpghttp://forums.avsim.net/user_files/104766.jpghttp://forums.avsim.net/user_files/104767.jpg

[Guest Fly II Pilot]

Georg,I guess I didn't fly long enough (maybe 20 minutes), to experience the fps degradation. However, here are two more changes that I forgot to mention, not sure if it will make any difference: a) I renamed fly.pyc to lfhc.pyc (in modulesscriptspythin) and I also renamed the scenery folder (in scenery) to huez. I did this per the English instructions for manual installation.Hope this helps!http://www.avsim.com/hangar/fly/dfdg/banneraa.jpg

[Guest HeliFLYer]

Hi Alejandro,the compiled Python script lfhu.pyc was already in ... Globals and changing the folder to Huez didn't improve anything.As I have several FLY! installations (which are all different but 240) I installed LFHU several times.I got all the same problems as described. I will test whether I have a different France SE elevation POD and reload it today from ROTW, but no big hope.Beside this, I don't like the automatic installer (my personal opinion, don't take this too serious). WHY?1. After unzipping you get a readme-file which is different from the readme in the folder "readme" which is installed. In this unzipped readme-file there is NO hint for manuell installation and no advice that a special readme-folder will be installed (with the other readme-file). I did not read the text after automatic installation as I thought I had already read it after unzipping - big error! It was you to give me a hint that there must be some other information and I searched for it.2. The automatic DEX-Import does not work properly if you have several different FLY! installations. Though all files were written into my FLY! on drive H: the automatic DEX-Importer reinstalled all the files again on my C: FLY-installation. I had to do (and could do it) manually.But after all, despite all the time I spent I won't miss that BIG and OUTSTANDING airport, great work, I had much fun making several landings and starts. I can live with those problems and want to thank you again very much for your help! Regards Georg HeliFLYer EDDW

[Guest laurentC]

Hi Gent,I'm not the author of the altiport improvement (it's our rotw fellow Fred) then I don't know if this post can help in anyway ...Nevertheless it seems that the USA version differs in any way from the EU version. Fred has made a special python pyc for the USA mesh ...lfhu_usa.zipYou can find it here (1Kb):http://rotw.simvol.org/beta/ (don't miss the last "/")Cheers,laurentC (rotw)

[Guest rene_35]

Hi gentlemen,I am the author of auto-setup for this scenery (based on Install Creator program). Some informations:- this is a new improvement, in beta version.- I have not provided the english version (this next week-end on simvol english pages)- I know there are differences between the readme, but remember, it's for a test of this new functionality.- this functionality has been implemented for non specialists who have only one copy of Fly! on their HDD (I wanted to upload the "usual" zip file, sorry not to have taken time to do this).- as you know, there is a deximport restriction about the folder where FLY! is: deximport modifies only the databases which are located in the windows registry "HKEY_LOCAL_MACHINESOFTWARETerminal RealityFly! II" (key word "Path"). You can modify this registry without problem with regedit. If you know a possibility to avoid this feature, I should be glad to have it.- another problem with "install Creator" program is to include one deximport.exe by dex file. I have not, for the moment, found a good solution._ there is another tool to create automatic setup: NSIS program. But it's more sophisticated (understand complicated). I've used it for the DVD (ready at the beginning of february).Cheers,Ren

[Guest HeliFLYer]

Hi Laurent,your post helped to solve the problem up to 95%, there are still some phenomenons but don't worry about that - it seems I am the ONLY user who had problems up to now we should wait an see. As for me there is much fun to fly the scenery/airport with some different smaller GA aircraft and all is ok now.BUT to make things clear I want to give some further technical information:I use the GERMAN FLY! II version and that should be the EU/international version!To make it work I had to change the elevations in the unpodded Scenery.S01 file (dataD004163) as Alejandro described aboveAND (!!!)I had to use the lfhu_usa file (although I have the German FLY! version).As there are 2 different versions of Beralex elevation France SE, one podded and one unpodded with *.scf files I tried both but NO difference (work both with changes, do not work both without changes). BTW I downloaded that from ROTW again to be sure to have the newest and I was astonished that it is the podded V1 version whereas the readme of the unpodded version says>>>>>>"El

[Guest HeliFLYer]

Hi Rene,thank you for your answer. Please take this discussion as it was meant to be - a feedback for further improvements and NOT as bad faultfinding.Automatic installation sure has big comfort and enables the "normal" user to get all sorted without errors (if it works). But you should give some information for the better informed user what your robot does, so that he knows what happens - I was VERY irritated when I by chance found 3 more versions of deximport in the FLY! folder, every 4 kb bigger than the original. Can you understand that I first thought of a virus which had changed and copied the Deximport.exe. I scanned all these files immediately but no virus was detected. It was after the second LFHU installation that I saw the connection between these files and the autoinstaller.There is no problem to use DeximportGUI and import manually LFHU_airport /_runway into EVERY other FLY! installation WITHOUT changing the registry, _waypoint is not possible because the database is lacking (is it a Volnav database???).After all thank you very much for your work and activity for FLY!, ROTW members keep FLY! alive.Georg HeliFLYer EDDW

[Guest Fly II Pilot]

Ren

[Guest Fly II Pilot]

Georg,The problem with waypoint is that it's actually called waypoints...http://www.avsim.com/hangar/fly/dfdg/banneraa.jpg

[Guest rene_35]

Hi all, first, you haven't the last SRTM elevations which are include with last Gap scenery. Look at the end of this page:http://fly.simvol.org/telechargement_fly2/...r/alpes-gap.phpthe new SRTM elevations are downloadable here:http://fichiers.simvol.org/fly/fly_2/France_SE_SRTMv1.zipSecond, this modules is not modified by Alpe d'Huez.I'll modify the "elevations" pageRen

[Guest HeliFLYer]

Hi Rene,THAT was the info which solved the main problem - I installed the SRTM elevations, changed all modifications back and it works fine.Thank you very muchRegardsGEorg HeliFLYer EDDWBTW: the SRTM elevations are worth downloading as "a stand alone add-on"

[Guest rene_35]

You're right Georg, it's fixed now, go to the "elevations" page (sceneries menu) at simvol (english or french version as you prefer).(And this year we'll have new TJ's textures on this area)Have good flightsRen