Posts by ApfelFlieger

I also find it best if as many files as possible are plain text files.

In the meantime, I do it this way:

- I use the new tool as a pure tool for the creation of the tap-file.

- Afterwards, I optimise the respective tap-file by hand; the new tool cannot do some things, at least not at the moment.

- When I have finished, I convert the tap-file to the tmb-/toc-/tsc- and wad-files.

- And finally I save the tap-file as an original file at the airfields as well, so that I can make changes at any time.

admin :

What is the new structure of the elements for objects?

        <[list_tm_airport_pd_custom_model][custom_models][]
        >

Quote from TomSimMuc

...

You can use my mesh and the ortho of IZ0JUB in the meantime ...

https://flight-sim.org/filebas…hd-scenery-february-2022/

In addition, here are my results for EDXH (Helgoland Düne Flugplatz) and DE0035 (Helgoland Insel Heliport) from the alpha test of the new tool for the FS4. Please consider this only an alpha version because of the points that still need to be corrected -- you can still have fun with it.

Please load the two directories into the user folder for aerodromes, e.g. on a Mac:

/Users/username/Library/Application Support/Aerofly FS 4/scenery/airports/de/

During the alpha test of the new tool, I also created the airfields from this project. Because the result is also still alpha, I am not yet posting it on Flight-Sim.org -- but anyone interested can try it out -- have fun.

Already with my airfields in FS2 I liked to take both the coordinates and the altitude of the airfield from the official charts.

=> Therefore, I would find it good if this data could be entered directly in the tool under Airport Data.

Overall, the tool is getting better and more useful for me.

I guess for runways the checkbox for skidmarks doesn't work because I can't see that there is a difference if they are on or off.

With the new tool, Milton Hospital can currently be realised like this; have fun.

For me this would be:

- FR0053: 3 helipads on a slope

- FR0347: Runway only partially visible

- LF2921: Runway only partially visible

- LF2922: Runway only partially visible

- LF2923: runway only partially visible

- LFRL (still in preparation!): Asphalt partially not visible

@ all:

For the parking position, the sizing works so well that if you select an aircraft that is too large, that position cannot be selected.

=> In general I find this very good.

=> However, it is now a matter of adjusting that one does not accidentally select the size too small.

Thanks for the info, some notes on this:

- The tool always automatically sets "0" for the elevation.

- At the moment I can only enter the height manually with a text editor in the exported tap file and then import it again.

- For small UL sites and heliports only it would make sense if the altitude worked there too. Currently, in these cases (e.g. FR0052, FR0053, FR0054, FR0461, FR0462, FR0463) no areas are shown - thanks to the good images from flightxtreme , however, this does not bother me personally at all in these places .

Using FR0046 as an example, I have asked two basic questions about elevation.

Using LF2922 (Base ULM de Poullaouen le Stancou) as an example (zip file attached) I show a problem with elevation conversion (tested with C172 and UH-60):

• Case 1 -- LF2922 is not activated:
  => take-off-positions 15/33: aircraft hovers slightly above the ground; no problems taxiing
  
  

• Case 2 -- LF2922 is activated:
  => take-off-positions 15/33: Aircraft sink; problems with taxiing
  
  

Also, the runway is only partially visible. I tried different altitude settings for both the airfield and the runways, but it always remained the same. Even when I set everything to 150 m, there was no change for me.

admin :

I have a general question about elevation, which I will show with the example of FR0046 Brest Amiraute Heliport (I have attached the data as a zip file):

• - 0 m -- automatically written to the tap file
• - 6 m -- FS4 at "Choose your starting location"
  
• - 2.12 m -- FS4 via CMD+F1
  
  
• - 1 m -- Google Earth
• - 2 m -- App Pocket Earth
• - 2 m -- App Maps 3D

Now my questions:

• What are the correct values for FS4?

• And which values should be entered for elevation ("<[float64][elevation][?]>")?

Unfortunately, my theory has not yet helped me in practice either.

To enter the height, I follow these steps:

- export tap file

- in the exported tap file enter the height by hand and save it

- delete the airfield in the tool

- import tap file again

This is also how I enter positions or orientations when I transfer them from FS2.tsc files. I also do it this way when creating military airfields with pixelated airfields - with success.

Quote from svdm

ApfelFlieger : I got the converter perfectly running using parallel Windows 10 virtualisation. Unfortunately it converts to FS 4 (FS2 is the only version that runs on my iMac late 2013 ... I tried )

I have researched again on the internet:🤓

According to everything I find, there is no way to run a Windows x64 emulation on a MacBook Pro with Apple M1 Max chip and ARM via Parallels☹️. Unfortunately, this only works with the Intel chips on my 2012 and 2018 MacBooks😊, but they are both with my grandsons.

Fortunately, my 15 year old grandson had some time last night to do some conversions for his grandpa😄. Unfortunately, this is nothing for a trial and error with quick changes of values.🧐

I have some Windows applications that run without problems with Windows11 via Parallels on my Mac. So far, only the applications from Aerofly fail because of the x64 problem -- unfortunately.

Quote from admin

@ApfelFlieger: Ok, we will check if we can do a native mac OS version. However both Parallel's desktop and VMWare Fusion can run Windows 10 x64 on your M1 Mac without any issues.

I have now tried to run Parallels with existing Windows 10 versions instead of Windows 11 -- but it always fails with the message that this does not work with the ARM processor on my Mac.

I think I'd better devote my time to the new tool and wait for a Mac version.

Quote from admin

@ApfelFlieger: We will check and see if we can provide a mac OS version. But keep in mind we require 64 bit here as well. You might want to try to install a 64 bit Windows version for your Parallel desktop program maybe?

My MaBook is "unfortunately" too modern and already has the "Apple M1 Max" chip and no longer the Intel processor. But the exe file wants an Intel processor for x64 with Parallels.

Additions after converting all my 23 airfields:

• The error with the missing symbol only occurs at KNHU and not at the other aerodromes with an ICAO code.
• More than 6 characters can be entered in the ICAO field in the tool. This is also converted accordingly. However, FS4 then does not find aerodromes such as FR-0046, but FR0046 is found.
  => A plausibility check should already be carried out in the tool.
• The "automatic" data export from the tool is done with capital letters.
  => The data export should also only be carried out in lower case letters.
  
  

I welcome the release of a Mac version as soon as possible, because then I can immediately check what the Tap file looks like "in real life".

I have just zoomed in with my grandson, who has my "old" Mac, which is x64 capable. I already have KNHU, the rest will follow shortly.

When searching for "KNHU", the airfield symbol in front of the airfield name is missing:

When selecting the take-off site, everything fits.

Now fine-tuning with the BRIGHTNES settings is required.

Shoot, now I'm failing the Windows processor because I get this notice under Parallels on the Mac: