Posts by crispy136

    Hi Nick


    I did some testing and comparison with the various files created by the manual FSET and automatic AeroScenery processes and after a few false starts I think I have an answer.


    I used the same FS2 level 13 grid in FSET and Aeroscenery and set about to produce the output, then compared the results. Both TMCs were run through Geoconvert with Mask enabled.


    Output files created- FSET = 1, AeroScenery 3 =3. Note all images below show FSET on the left and AeroScenery on the right.



    The extra ttc (70a0) created by AerScenery was a strip across the bottom of the tile, hence the additional mask file needed. Looking at the source stitch file, the texture is from the top of the stitch image, so it in effect fits on the top of full tile created. Look at the enlarged image below to see the strip as the thumbnail process chops it off. Running the extract with masks off would have seen the mask tiles not created. I had found in my earlier scenery creation attempts that when a source image spanned multiple grids in FS2, and you are running GeoConvert for that grid level with masks off, then Geoconvert discards those tiles that would have resulted in a partial tile (mask tile). Same thing occurs with transparencies.



    TMC comparision - no difference here


    AID files - difference in lat of the top left coordinate, the first clue I think.



    Lastly I compared the source graphic files created from the image data that is read by GeoConvert. What I found was the AeroScenery stitch file was taller than the compiled BMP created by FSET. The AeroScenery stitch image has a horizontal strip of image at both the top and bottom compared to the FSET file. In the AeroScenery stitch image the extra strip at the bottom is roughly double the size of the extra strip at the top. In the image comparison below note the small creek at the bottom right of the AeroScenery image, and the small oval at the top. Both these are missing from the FSET extracted image. The width is the same in both.


    Source image comparison - note extra height in the right image created by AeroScenery


    When running GeoConvert (using an identical TMC file for both remember) the extra strip at the bottom of the AeroScenery image appears to be ignored by Geoconvert. But the extra strip at the top of the AeroScenery stitch image appears in the additional files created by the mask option. I am assuming that as the FSET source image file more closely matches the FS2 tile's width to height ratio, no mask files are created as there is no additional image area to be cut off.


    Raw file comparison of the same output file produced by both processes - both are identical except for some colour variation. The top and bottom of the AeroScenery image is discarded by GeoConvert resulting in the same output image as from FSET.



    So there appear to be 3 courses of action.


    1. Do nothing in AeroScenery and just run with masks off. This will discard the extra portion of the taller AeroScenery image. The top section of the image used in the mask file has a distinctive oval in it, so I was able to confirm that this strip also appeared as the bottom section of the full image of the tile above when that grid was extracted. So using masks off and discarding the additional image data will not compromise the scenery output accuracy. But using masks off will cause problems where transparencies are used.


    2. Do nothing in AeroScenery and run with masks on. This would mean that FS2 has 2 image tiles created for the same data for the same level. So the images in the strip across the mask tile will also appear as part of another full tile. Not sure if that has any impact, but I did read in another thread that mask file sometimes cause visual issues in FS2. Can't remember the issue though.


    3. Modify AeroScenery to reduce the overscan in the stitch file. Masks can be left on to allow for transparencies and this will not impact the output file creation as it does now.


    The image below shows the size and coordinates used by FSET that produced the FSET equivalent of the stitch file. Perhaps you could compare these details with that used by AeroScenery.



    Just as a side point, but I had to run the FSET process a couple of times to try and get a good match of the respective output file resolution. I had to try different download sizes in FSET to match the zoom level in AeroScenery, since they describe the image quality differently. I ran 3 extracts in total at different image quality levels and in just one of those, the FSET data produced mask files. However when I looked at the mask file it was just a single line of pixels across the bottom. So FSET occasionally has some very small variations that produce mask files, but they are rare.


    I have been looking at this so long my eyes are starting to bleed. Time for a break.:)

    I'll try using the old FSET process for the same grid square, with masks on and see if I get the same results as AeroScenery. If I get the same problem, then it might just be a Geoconvert limitation caused by using masks. In that case the solution would just be to disable masks unless you really need them for transparencies. If I don't get the problem using FSET, then comparing images created and TMC files uses might point to a solution.


    I don't think the FSET tool was developed by IPACS, as it can also be used for FSX. My guess is that IPACS built Geoconvert around using FSET as the data source.


    Couldn't find the disable masks option you mentioned. I thought it was in the settings screen in 0.4, but is missing from that screen in 0.5.

    Thanks Nick


    The google link is https://www.google.com/maps/@-…3603,60000m/data=!3m1!1e3.


    I don't think the decimal points are causing the mask issues. I have been extracting image data using FSET and using a little utility to align the images extracted co-ordinates in FSET with the FS2 tile sizes. FSET would no doubt have to trim downloaded images to fit the FS2 tile size when it stitched together the images for Geoconvert to use. The TMC file was generated using another utility using the same co-ordinates as the FSET extract and only used 2 decimal places. When I used this method everything always lined up and no mask files were produced. I usually run Geoconvert with masks off, and the tiles always line up in FS2. I only ever use the mask option if i have a file with a transperancy.


    I see the mask option has disappeared from the setup screen, so I assume it is on all the time. Perhaps I could manually edit the TMC file, then run Geoconvert and see if the issue goes away.


    I have rerun the first 2 grids individually and still got file name conflicts, so the problem is not multiple Geoconverts running at once. Have attached some screen shots of the output so you might get a better idea of the problem.



    Thanks for the updated program. No problems running it now.


    Gave it a go for a level 14 tile selected, level 14 also selected to be generated by Geoconvert and zoom level 18. The output had some mask files, which Geoconvert usually only produces when your source image selection size doesn't match the FS2 tile size or transparency is used. Looking at the PNG files produced I see that there is a small strip across the top which has spilled over to another tile. It looks like the level 14 tile in AeroScenery and FS2 might be a slightly different size. Re-ran this using zoom level 19 with similar results, although I got less mask files. Used both Bing and Google with the same results.


    Also tried running download, stitch, generate aid/tmc and geocovert all as part of the one selection. This combination of selections failed in ver 0.4, but ran perfectly in ver 0.5.


    Ran AeroScenery for 12 level 13 tiles, zoom 17, Geoconvert level 13. Mask issues occurred again with level 13 tiles with a proportionally larger strip spilling across to the tile above, resulting is extra files and mask files. With 12 grids selected AeroScenery kicks off 12 Geoconvert sessions at the same time. This maxed out the CPU and stopped all other activity. All sessions finished without issue though. If a batch session could be implemented in a future update, it would allow the PC to function normally while the process is running. When copying the result ttc files across to FS2 I notice that were some duplicate files created. For instance grid 1 and grid 2 both had a file with the same name, although the content was different. The grid 1 naming convention was used for one of the tiles in the grid 2 folder. The grid 2 file with the grid one name was one of those files with just a strip across the bottom, so seems to be a mask issue.


    Loved the ability to select the different map view types. I did get myself confused when I was able to display google on the maps but had Bing selected on the extract.


    Great update.

    The shoreline water is a problem unrelated to AeroScenery as it also occurs using the more labour intensive FSET process. Editing the source graphic files is the way to go, done just before you run Geoconvert. Had a similar problem for some coastal areas using Microsoft's Bing data with areas of white and differing tile overlaps.


    There are 2 ways to deal with this. Options 1 is to do as suggested by Jetjockey10 and overwrite the problem areas. I used a simple cut and paste in GIMP to accomplish this, and used this when creating level 9 and 11 tiles. Options 2 is to get rid of the problem areas altogether as a transparency, also using GIMP. I used this method when created more detailed images for level 14. Note that when using transparencies, you mast have masks enabled or Geoconvert just skips any tile that would have contained the transparent section.


    One other issue I have noticed is when using Google maps in AeroScenery as the data source, you get google logos appearing in your scenery in FS2. They are most noticeable on water but they are present on the land as well. This was extracting the images at zoom level 16 (4m/pix). Higher zoom levels used to create a level 13 or 14 tile would no doubt make this more noticeable. Bing doesn't seem to use logos. The same area extracted using Bing had better colours and no logos.



    Decided to give Aeroscenery v.04 a go.


    Ran AeroScenery with Google & zoom level 16, level 9 & 11 AFS levels, with "download imag tiles", "stitch image tiles" and "generate aid tmc" selected.

    Findings

    1. Really loved the GUI and ease of use, saved heaps of time. Thanks for developing this program.

    2. Once you set the geotools folder in the settings and then exit the program, Aeroscenery will not start again. Deleting the AeroScenery registery line allowed the program to run again, but you have the set up the geotools folder again. However after a successful processing run, this problem does not reoccur, and AeropScenery starts every time.

    3. Hitting stop after the program has been running doesn't clean up any files it created.

    4. Found the program errors if you leave the default setting that includes "Run Geoconvert" selected.

    6. I ran the program 2nd time with Run Geoconvert deselected. It downloaded all the tiles again, overwriting identical files, but finished successfully.

    7 Log from file download is overwritten with stitch details once that process runs.

    7. Ran with just "Run geoconvert" selected, but Geoconvert only created level 11 files while I had selected 9 and 11. Tried again with just level 9 selected but Geoconvert only generated level 11 filesagain.

    8. Grid appeared in FS2 OK, but Google textures are a bit washed out compared to the textures created with "Virtual Earth" & FSET.

    9. Tried it a second time with Bing instead of Google (all other values the same) and interestingly this generated both level 9 and level 11 files. Images below show tiles from the FSET & Virtual Earth on the left and the adjoining tile on the right was generated using AeroScenery & Google/Bing. Might just be season/time of image. Bing is closer to Virtual Earth, but both are less vibrant that Virtual Earth.


    Virtual Earth/Google



    Virtual Earth/Bing

    Hi Clayton4115


    The file list looks OK from what I can see. I deleted YBBN from my PC and downloaded it again from Fscloudport just to be sure and it all worked OK in FS2.


    During development I encountered disappearing buildings after I had added some extra detail. I edited the airport in Fscloudport and deleted a few things and the scenery was OK again. So it appears FS2 has a limit to what it will show and I had initially exceeded that with YBBN using Fscloudport.


    So it might be a memory thing. On my system with 4GB video and 20GB ram it works OK in its current build. And that is with all my development programs open as well on Windows.


    When I had too much detail in Fscloudport all the buildings disappeared, leaving only the runway and tower. Is this what you are getting?


    I also notice you are using a different folder location to that recommended by Fscloudport. If my other airports worked in the same location then the folder isn't an issue.

    Have been loving FS2 and its photorealistic scenery, but the lack of Australian scenery has been a major disappointment. So the only thing to do was create some myself. I looked at all the tutorials available and gave it a go. After a very steep learning curve and some help from the forums, I managed a grid from Byron Bay in the south to Noosa in the north and Toowoomba in the west. After creating all the textures I have also used the excellent Fscloudport to create some individual airport buildings, runways and static aircraft for Toowoomba, Sunshine Coast and Redcliffe. The textures for the whole region are suitable for flying above 3000 feet and I have added higher quality textures around the airports for lower air work. The textures look great from the air but the appearance is a bit flat at ground level, so the Fscloudport detail at airports brings it back to life. Any texture colour variations are a result of the available imagery.


    I still have to add airport buildings to Gold Coast, Caloundra Airport, Archerfield, Caboolture and Amberley. All airport details will be limited to that available from Fscloudport (due to my skillset and inclination). Brisbane airport itself is unlikely to have significant building details added due to the complexity of the terminal, but will do hangers etc. After that I'll start working my way north towards Cairns. The texture size is about 320MB for the main area textures for the area, between 40MB to 120MB each for the detailed textures for airports. The Fscloudport buildings etc are a quite small download with Sunshine Coast airport coming in at only 5MB The finished airports are already available for download at Fscloudport, but they don't include ground textures. Haven't thought about how I might distribute all this yet.


    It really is impressive when you can pick out your own house as you fly over, so naturally my own place is in one of the high detail areas, but more by good luck than by good planning.


    It is still very much a work in progress but thought I would share some screenshots for those Aussies out there hanging out for some Australian scenery for FS2.


    Sunshine Coast



    Maroochydore



    Sunshine Coast Airport - buildings created with Fscoudport



    Amberley Air Base - textures only



    Gold Coast



    Mount Tamborine



    Brisbane from 35000 feet



    'Redcliffe Airport - buildings created with Fscloudport


    Toowoomba City Aerodrome - buildings created with Fscloudport


    Thanks Ed. Fscloudport looks like a easy way to enhance the visually impressive scenery created using Geoconvert. 3dsmax and AC3D are a bit advanced for me at this stage, although I have viewed one of the tutorials for AC3D anyway.

    Thanks Ed


    That worked just great and the airport is selectable in the Location menu. It didn't create any visual runway just the option in Location so I guess that is a separate process. I see there are video tutorials on that.

    I made all the Lon Lat corrections but still no luck on seeing the airport in the Location screen or when flying over the location. Corrected TSC attached. I am wondering if maybe FS2 doesn't support airports in the southern hemisphere, although the images work fine. Any help would be appreciated. yred4tsc.txt

    Thanks whitav8. :)


    I hadn't noticed that the program developers has swapped the usual Lat Long for Long Lat. Obviously a rookie mistake by me, but I wonder why would they did this anyway? This would also explain why my TMC file wouldn't produce any image files initially, as I caused the same problem there. It was only when I used the excellent 'Convert FSET to Aerofly TMC File' web page that I was able to get image files created for FS2. I had wondered why that worked but my original TMC didn't, but hadn't noticed anything obvious when I compared the 2 files.

    I was successfully able to create some scenery for my home area of Brisbane, Australia using the scenery creation part 1 tutorial. It looks pretty amazing in FS2. Now I now want to add an airport to my scenery. I followed the airport tutorial and created a TSC file, placed it in the places folder, but the airport never shows up in FS2. Not sure what I am doing wrong. Have attached my TSC file for reference and have renamed it from tsc to txt to allow it to be attached. I have tried creating the file with both Notepad and Wordpad but nothing I have tried works.


    Can anyone advise what I have done wrong?


    yred2.txt

    Thanks Jan, I also noticed that the reduced NP setting for the prop levers is not working. You can set the reduced NP setting for the props and it is confirmed on the centre display. When you increase power, the NP notification on the centre screen disappears as you would expect, but the props setting does not automatically increase to maximum and just stays at the reduced prop setting. I have used this feature in the past successfully on the Dash 8.


    Regards, Chris