edgarone

@dburne - this is not working: automatic login is not enabled, but I cannot get past or ignore the login - either I login or stay at the login screen. Logout during the game sends me back to the login screen.@Richdre - This might be a good workaround ! Thanks!

Well, I find this quote sligthly misleading: It seem to me, when you downloaded, you can play offline on the single island and the single plane - as long as you wish.As soon as you logged in for the first time, you cannot longer play offline, but must login and stay online - otherwise you bounce back to the login screen.Until now, I did not find any other way - I am not able to play offline and without login - exactly as described by George.

Are there any clandestine missions on the main island only (no Hawaii adventure pack) ?

I find it slightly annoying, that I get a loading screen, when I switch back from the map to the cockpit... I think, this could be improved.

Just switch to the map ("M") and back - then it shows the actual distance in that moment.

Each simple scenery is basically a parent-folder with the sub-folders "scenery" and "textures".To use that scenery the parent-folder must be added via the Scenery Manager. Physical location of the parent-folder can be anywhere. 1) The (default) parent-folder "Addon Scenery" already contains both sub-folders and is already added via the Sceenry Manager. Each single scenery and texture file you put into the sub-folder will be recognized and used after an restart of the FS. 2) If you put a "complete" scenery with parentfolder/subfolder _under_ the "Addon Scenery" folder, you have to add the "new" parentfolder with the Scenery Manager.

Hello Cativo,scenery and excludes were working before you upgraded from XP to W7/64 ?It should not matter, which OS you use to run FSX. FSX is interpreting and displaying the scenery files, not the OS.Is FSX and scenery new installed after the OS upgrade?I would check, if all scenery and exclude files of your scenery are still there and included in FSX and I would possibly check the order of scenery layers.

Hello,I read this latest review on Avsim with interest and enjoyed the pictures showing this model in the environment of FSX.Especially those close-up shots showed the care, which was given to the details of this model.There is a saying, that one picture is worth more than 1.000 words.Well, in that case we got more than 7.000 words about the installer. And for an installation, which is described as "extremely simple" this is a little bit too much in my personal opinion. I believe, it is not necessary to depict in a product review of a helicopter model the installer with a number of pictures, which show us EULA pages and even a installation progress-bar, when the only variable in the whole installation process is the path of the FSX installation directory.Sorry for bean-counting, but I personally would have enjoyed it more to see additional pictures of the product itself.But anyway, it was nice to be introduced to a new interesting helicopter model by this review.Thanks and keep up the good work!Regards,Edgar

Hello,I read with interest the recent review of the C-130 Hercules by Jason McKee.I completely agree, that this is a quite impressive model, which is fun to fly and to hear (the sounds - great!).Unfortunately I am not completely happy with the review itself. Although it is always nice to have pictures showing details of the product, I personally do not like to see all screens of the installer. If it is a very "Very Simple Installation Process", it does not make sense to me, to see the installer pictured in detail. What is the point of having 9 desktop screens with different install windows in a plane review? I can see, that the installer has an EULA page, but cannot read them anyway, because it is too small...The same applies to other reviews like "VFR London X" or "Bellanca Viking Collection".In my personal opinion this is not necessary.However, I have some other remarks concerning the boxed FSX C-130 version of Just Flight:The Aircraft Configuration Editor seems to have problems with permissions and accounts (at least in Vista).I installed the addon as an Admin user und use it as an user (2) with limited rights. The user (2) is not able to read some registry entries of the addon - resulting in several error messages, when starting the ACE and finally empty pathes for the FSX install dir and for the FLT flight files ("tools" page). It is also not possible to enter and store the correct values here. Probably the ACE program is not fully compatible with the Vista permission system. But thats only my personal assumption.However, the plane is usable out of the box in FSX, even as user with limited permissions.Just another remark concerning the modules and instruments: After a crash it is not possible to start a new flight and use radar or autopilot. It was not possible to turn them on and use them. I had to restart FSX completely.Well, thanks for providing us with interesting reviews - keep up the good work.Kind regards,Edgar

Hi Chris,please check, that you have the latest TDFHeaders.inc and TDFMacros.inc Header files in the Ground2k directory (available here at Avsim)! My copy is from 12/17/2003.I was able to compile your file without problems (see attachment).ASM Macros like VTPChildPoint are defined in these INC files. BGLC is basically the MS assembler, which compiles the source code text into the binary BGL files.Best regards,Edgar

Hello Chris,btw. you should check the FS2004 SDK for informations, if you want to create sceneries for FS9.I assume you use Ground2k4 with the latest patches (available here on Avsim).Ground2k4 produces a temporary file in a ./Temp/ folder under the ground2k4 installation folder (or in the Ground2k folder itself) . It is called "Ground2K$_Lines.ASM". It is overwritten and new created everytime you press "compile" in Ground2k... This is the actual sourefile, which gets compiled into a BGL files for road lines.Can you compress it and attached it to your answer?However, be aware, it would contain the data for all the roads you created in your project.Kind regards,Edgar

Hello,in former versions of FS (I think until FS 2000) you could see the Berlin wall, if you turned back time before 1989.Regards,Edgar

Sorry Tawni,I didn't saw, that you created a new own folder under /addon/...So it is indeed suggestion 2.Regards,Edgar

Hi Tawni,when you put the exclude file in the same folder like the original scenery, which creates the buildings, you must take care of the execution order: first create the scenery, then exclude the buildings.Inside a folder the execution is alphabetically ordered. So you must use an exclude filename like ZZ_exclude.bgl to put it at the end of the queue.Or use an additional scenery folder and give it a higher priority then the default scenery folder in the scenery manager.Or you might just use the addon scenery folder, which is usually on top of all default scenery folders.Best regards,Edgar

Hi cbuchner1,although it sounds interesting, at least as a kind of online service, where you don't have to store everything on the harddisk, it seems a little bit difficult.I think, there is no ordinary database used. At least FSX do not come with ODBC drivers, right. And no db engine is started before FSX.I don't think, it is needed for your goal, to change or hack the library files itself. Rather have a look at this file in the parent folder of the /scenery folder, which gets updated at startup ("rebuild scenery database") , when you change the data (the library Bgls) in the scenery folder.I could imagine (pure speculation!), that this cache file contains basic information, what data to expect in the scenery-folder (100 points of road-vector-data for an area around coordinates x,y etc.).I think, these (summary) files are loaded during startup and stay there in memory.You might create dummy files, which describe data, which is not actually in the scenery subfolder, but must be downloaded.But then you must deal with the startup task, which scans the disk and rebuilds these cache files during startup. And which tries to open the files in the scenery folder.You might have another look, if the old scenery caching mechanism still works, where you didn't copy all disks at installation time, but rather copy the data during the startup, store it in a cache folder and delete the caches, when stopping the sim. Regards,Edgar

Good morning, Bergziege,when you don't get bgl files after compilation, it is often a sign, that the compilation process fails - for various reasons.Please check, that you have the latest TDFMacro files from Richard "Rhumbaflappy" Ludowise (available here in the library). Replace the old copies in the G2k folder.BTW: I can compile your sample project and receive a *_9.bgl file.Best regards,Edgar

Hello Luis,thanks for your answer! I already extracted it from the original SDK.What a pity, that it is more difficult now, to correct the occasional flaw in the default sceneries!Best regards,Edgar

Hello,it seems to me, that the list with scenery objects "D:fs2kMicrosoft Flight Simulator X SDKSDKEnvironment KitAutogen SDKlibrary objects.txt" is replaced by an Html-file, which only contains the generic objects, which can be placed anywhere in the world.The list of local objects and GUIDs for the Berlin, London, Paris etc. objects is gone.Is there anything else lost as well?Best regards,Edgar

Hello Luis,thanks for your answer! In my first testfiles sent to you on Friday I just wanted to exclude one single building in Berlin, which is not a library object, but a generic building. This is displayed in the scenery, even when the autogen slider is at 0, but has no unique ID.I stumbled over the problem, that this "excludeGenericBuildingObjects" rectangle must be the first in the list of rectangles.The second testfiles (here in the forum) are used to test the autogen-exclude-problem ("ALL") from Lars. I do not want to exclude 2 whole areas in Berlin - they are just a test sample. I just want to exlude autogen in one small rectangle in (13206,31413), but this doesn't seem possible with BGLcomp code now.But what I find quite strange, is that using both exclude bgls in the addon-scenery folder didn't work either and excluded only one rectangle. However, I didn't test 2 bgls with just a single rectangle each.What I want, is a chirurgical knife to exclude objects in a small polygon, not a wooden hammer to flatten whole countries.Looking forward to a small description, how to create excludes with shape2vec... :DBest regards,Edgar

Hello Luis,could you please tell me again, what is the difference between "normal autogen" and (not normal) "forest trees"?And how do you "turned off the xml autogen file"?I came to the same conclusion about the size of the exclusion rectangle: it must include at least a full area. When 1,5 areas are enclosed, only the autogen of the full area is excluded.Maybe this explains your problem with the not excluded edges.(all other rectangles (for library objects etc) can be smaller and more precise)And I still have the problem, that only the first (FULL) exclusion rectangle is recognized and a second one is ignored.Even putting 2 exclusion bgls with 2 switched rectangles into the same scenery-folder did only exclude one area (see the attached sample).PS: I have the same problem with the double quotes: When I do copy and paste the samples from the SDK, they do not compile until I change the double quote character.It might be a problem with the character sets of international Windows versions?Best regards,Edgar

Hello JuiceRabbit,which FSX SDK are you using?Best regards,Edgar

Hello Merv0728,it looks like the documentation FS2004BGLCompSDK.doc (my copy from 17.02.2004) is not fully correct here.If I interprete the xsd file 'bglcomp.xsd' correctly, is the element 'Apron' defined as type 'ctApron'.'ctApron' has an indeed element called 'Vertex' , which has the type 'ctVertexLL'. 'ctVertexLL' has two elements 'lat'/'lon' - there is no Vertex element from the type 'ctBias', which would allow biasX/Y/Z here.Best regards,Edgar

Hello Norman,I never was able to produce LC files with G2K4. Although it works for WC files.However, if I remember correctly, you find the LC/WC raw file, the LC/WC tmf file and the .inf file in the temp or work directory of the G2k4 program folder. So you can manually compile the LC/WC bgl file - see the SDK.I don't know, how to correct this problem with G2K4. (I use G2K v3 to produce the LC file)Best regards,Edgar

Hello Luis,I had a look at my copy of the ground2k4.ini file, but didn't see any obvious difference. Although I was able to destroy and repair the function of the line-texture-id box with changing the value of "Lt_Rt_Effet", there is a more radical way to repair the problem:After closing the application ground2k4, you can delete in the file '(ground2k4-folder)/Resource/Ground2k4.ini' every line starting with "Lt_Rt_*" and "Lt_L13_*". The next time you start ground2k4 and open and close the object dialog box, the values are restored to default values and the lines in the ini-file are rewritten.Maybe someone else can check this out on his copy (keep a backup!) and confirm it.The problem seem to be caused, as Luis said, be selecting any value in the "airport/park" line box and leaving this page of the dialog box.The question remains for me, for what are these textures good for anyway - they seem to have an equivalent in the landclasses...Best regards, Edgar

Hello Luis,unfortunately I have no access to my copy of g2k4 until the weekend.I'll send it to you on Saturday.The compilation seemed to be fine. But I didn't checked the result bgl in the FS.I made a simple test project with 3 rectangels: a line, a VTP2 landclass poly and a VTP2 'airport/park' polygon.The resulting asm file contained 2 polygons: one with the texture of a landclass id (i.e. '24') and a second polygon with an 'airport/park' texture id (i.e.'1183'). The asm code is fine and compiles. It is identical, just different texture ids. The 3rd rectangle formed a line (as expected).Best regards, Edgar