• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FS2004 FS9 problems with AFLT version 4.3.04

4.3.06 is virtually identical to the version I sent - except that it fixes the issue you reported, Simon.

It's not clear how those "empty" placements found their way into the Placements.xml file. Did you start with data from a much earlier version of AFLT or have you done a lot of deletions/edits. If so, what version or which objects?. While such placements will forever now be ignored, I'd sort of like to know how it happened.

Tom, an invalid scenery path now elicits an error message as you suggested. It should have done so before, but I was only checking in one place for validity when I should have been checking in two.
 
Don,

The airfield lights in all my FS2004 airports were origonally done using AFLT versions 4.1.16 or 4.2.16 with no problems observed.

As I'm not sure what your looking for, I have posted one of my previous projects (LICJ Palermo) made with an earlier version so you can experiment/inspect.

I will try and assist you to sort this problem out as much as I possibly can but I'm not a software guru.


Reagards Simon.
 

Attachments

Thanks, Simon. Those .bgls won't be of much help since they are "after the fact". What may be helpful if you still have it is the Placements.xml file from the Project Folder.
 
Sorry Don, I thought they might be of no use after I posted them, I'll zip up a copy of the placement xml files from both versions of AFLT and post those later, I have been redoingthe ligting of all my airfields using version 4.3.06 with no problems evident, so thankyou for a quick fix.
Just one question regarding wigwags, I notice with AFLT they only function during darkness but not during daylight/low visability conditions, I have done some research online but can't find anything regarding regulations of their operation, your comments will be welcome.

Regards Simon.
 
Wigwgas should be operational all the time (that the airport is open). I thought those in AFLT were on all the time. I'll check in the morning. I expect to make a bug-fix release tomorrow. If there's a problem with wigwags, it will be fixed.
 
Don,

As promised I have attached two zip files of the LICJ Palermo project, one file was made with version 4.2.16 which allows the deleting/placing of runway edge and CL, the other file was made with version 4.3.04 which will not allow placements of runway edge and CL, I hope you can make use of these files in fault finding. I f you require any other files just let me know.

Your comments about the wigwags is noted.

Regards Simon
 

Attachments

Glad I can be of assistance Don, if you require any other AFLT files I have just let me know, hope you manage to find what your looking for.
 
Simon, I found a copy of 4.3.04 and tried it. Sure enough, I couldn't add runway lights either. But, there is no such issue in the latest release.

The contents of the two Placement.xml files you sent are identical, so they're not the issue. The only thing I can think of is that the current release handles the interpretation of the stock lighting differently that 4.3.04. So, if you've updated to 4.3.07, you should no longer be having this difficulty.

Thanks for your help.
 
Don,
I did the same comparison of the placement files and also couldn't see any difference too, I have redone all my airport lighting using AFLT version 4.3.07 and have not observered any problems, so many thanks for your assistance with this problem. You haven't commented on my observation regarding the wigwag lights though, are they now avialable during daylight?
Regards Simon.
 
I have just checked and wigwags. They once were, but now are not on in the daytime. They should be - and will be in the near future
 
I've got AFLT "torn apart" at the moment tracking down another issue. So I won't be able to release until I resolve that. In the meantime, if you shut down AFLT, open the Placement.xml file, do a search on "Wigwag" and replace "Parameter flags" (which probably is "00000010") with "00000050" and recompile, the lights should come on in the daytime.. If the flags are other than "00000010", just change the 1 to a 5, i.e., set bit 6.
 
Many thanks for the tip on the wigwags Don, I have bit 6 of the parameter flags from 1 to 5 and now have wigwags working in daylight and they look good.

Regards Simon.
 
You must log in or register to reply here.
Back
Top