FSwidgets, if it still works with Aerofly FS 4...
Works for me.
FSwidgets, if it still works with Aerofly FS 4...
Works for me.
In German I recommend this page for the A320:
Work for me (MacBook Pro):
- RJCC (Sapporo)
- RJOO (Osaka)
- CZBB (Vancouver)
I recently discovered that with the current FS4 beta I have to zoom in very far in the location map before I can set an aircraft's altitude to level GND.
From memory, I think this wasn't the case before and I could choose GND from any zoom.
To do this easily, you would need a standard kit for floor markings like for trmacs and lines.😀.
The light settings for the buoys are in the directory "as_hk_hk0000_hong_kong_addon/water_buoys" in the file "lighthuse_light_cultivation.toc", which I am attaching as a ZIP file.
The TAP and TSC files as well as uncompiled TOC files can be opened and modified with a text editor. I started years ago with small steps and gradually moved towards my current knowledge.
The TAP file must then be compiled into the 4 files TMB, TOC, TSC and WAD, as I write in the accompanying text. This is quick and easy.
The additional TSC file (with a different name than the TAP file) with data from FS2, if present, does not need to be further compiled.
I consciously always publish the TAP files for my airports in the spirit of an open source concept. So everyone can see how something is programmed by me in detail. And I'm happy about everyone who does the same. This way you can easily see how others do something - and you can also build on what already exists and easily adapt and further develop it for yourself. My wish for IPACS is that IPACS also publishes the TAP files.😀
Here is an example of how lights in FS4 can be called up via the TAP file:
A call via a TOC file is also possible, although the TOC files usual in FS2 have to be integrated differently in FS4.
Some notes on the individual lines:
165:
- the RGB values can also be entered between 0 and 1 with decimal places
166:
- the intensity goes from 0-♾️
167:
- this is the most complex setting because three different parameters are entered here
168:
- unfortunately, so far I have only found the difference between the values 0 and 1
=> I'm missing a value for a glow during the day
The lighting effects can be freely programmed in all respects.
I'll write later how it works.
Perhaps an expert in elevation mesh can help better map the topography of Hong Kong.
And last but not least, I uploaded 1 airport and 26 heliports for Hong Kong:
I have also uploaded a new version of Hong Kong-AddOn:
The EDITION 2024-01-09 unfortunately led to many error entries in the tm.log file. The revised EDITION 2024-01-09 only has 2 errors caused by the building "city_intl_trade_exhibition_centre"; the 3D container ships in the harbor were left out and the harbor cranes were converted to XREF (and their number was almost doubled).
I have uploaded a new version of VHHH(ex) KAI TAK INTL AIRPORT:
This contains the tower beacon light as well as the approach lighting of the RW13 located in the curve.
This also works for me on the iPad:
...
-Cold and dark positions possible at any ground location
...
By "any ground location" do you mean every parking position from the list?
In my opinion, the ACT beta does not yet have some elements integrated and these have to be integrated manually. For me these include:
- tower view
- lights
- carlots
This is how I currently do it for lights:
- I use a line type that I don't otherwise use as an auxiliary line
- where I need the position data, I set the handles of this auxiliary line
- then I export the TAP file
- now I add the light elements and take the position information from the auxiliary line
- I then convert this tap date
Things are going quite quickly now. I just have to make sure that if there are changes in the ACT, I integrate my manual additions back into the TAP file exported from ACT.
I realize that I should finally take a break from creating airfields and write some instructions. My improvement list is also still waiting.
Ich habe mit Aerofly FS 4 Version 4.03.03.04 (20240105) keinen Absturz auf dem Mac.
The reason is relatively simple:
In the original, VHHH KAI TAK INTL AIRPORT was decommissioned in 1998 and VHHH CHEK LAP KOK AIRPORT was put into operation instead.
In the simulation, IPACS therefore also saved the correct data from today under VHHH.
In contrast to reality, IPACS would now have to record the data from KAI TAK AIRPORT under a different ICAO code such as VHHX. The highlight would be if the IGS were programmed for RW13 instead of ILS. In my opinion, it would be enough to set up a fictitious ILS on the CheckerBoard.
However, I understand if IPACS does not want to make this effort at the moment because other points are more important.
I'm currently successfully working on at least supporting the approach with an optical light guide like the one in reality.