• 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 Can't Get Started

Thanks for summarizing. Re your item 5, I have noticed that from time to time (and confirmed it a moment ago). I'm glad you realized it's directional. It happened every 7 seconds. Likely due to some cyclings of the Tick18 timer.

Everything is "on my list".

Re your latest post, I know what that is. Until yesterday, that approach light bar was not shown. When I realized it wasn't showing, I forced it on. Apparently, I didn't set an azimuth. It too is on the list.

Don
 
Hi,

And that light bar is also one of the objects that is suppressed by an exclude file. I had to remove my new one to see it.

7.
a. Load or Create Project.
b. View/Stock Data
c. Delete Project
d. The Project menu is inaccessible ("You are viewing Stock Data. Project menu functions are only available when project data is in view")
e. The View/Stock Data menu item is grayed out and not available. At this point I think I have to quit and start over?
 
From above:
4. If the taxiway has a designator, only one side of the runway is lighted, so that is correct. So this applies only to undesignated taxiways.
 
At this point I think I have to quit and start over?
No, just deselect View/Stock Data.

Thanks also for the update re undesignated taxiways. I'm working that issue now.

Don
 
Hi again,

I cannot duplicate my problem #7, so I assume it was just a glitch.
 
Last edited:
I cannot duplicate my problem #7, so I assume it was just a glitch.
Curious. With 4.1.11 or later, you should not have been able to Delete Project (or anything else from the project menu) while viewing stock data. Anyway, it's gone.

Re the misalignment of the threshold bar, I have found the cause. The outer lights on those bars are toed-in 4 degrees , which is the magnitude of the alignment error. Somehow, that toe-in is being applied to the orientation of the entire bar.. Something to do tomorrow.

Don
 
Hi,

That screen grab in FS2004 back on page 3 shows a row of uni-directional spotlights pointing away from the runway (they have green lights). These were created by the Use Stock Lights command. They use the light type of Approach. Adding Threshold Lights to a runway does not create such a line, they use the Split type (only) and thus must have lights shining towards the runway as well. So, as a workaround how do I get Approach lights when I want to create a string of such lights anywhere I like? I can't seem to find the option to create such a string. I don't get the option to choose the Approach type of light in the drop down box when I right click the airport.

Thanks,
 
Oops!!! Looks like I've still got some work to do on Import of approach lighting systems. Tomorrow.

In the meantime, you could add the red bar by creating a threshold bar for the primary end of the runway using Dark/Red as the color combination.

Don
 
Hi,

When I said Threshold Lights I meant Threshold Bars, so don't worry about that. Threshold Bars can be added separately, Threshold Lights are part of the approach lighting.

So I can just create an approach with only Threshold Lights checked and get my string of green lights that way. I don't see a way to get such a string with other colors though.

And I didn't notice that Dark is one of the available colors, very handy to know.

Thanks,
 
BTW, it seems very easy to get into a situation where you create approach lights, but they do not add themselves to the map.

This is what I did:

1. Load project.
2. Select runway (red).
3. Choose Delete Approach Lights.
4. Choose Add/Edit Approach Lights.
5. Create MALSR approach lights.
6. Click Place Lights.
7. Box disappeared but no approach lights are displayed.

I can no longer get approach lights to be added to the map, even if I try again after re-selecting the runway or changing projects. I have to re-start the program.
 
Last edited:
No need to delete before you edit, not that I think that has anything to do with the result you experienced.

I've never experienced such a lockup. I'll check it out tomorrow.

Don
 
It’s not a lockup - the lights just don’t appear.
I just followed the sequence of operations you outlined above. No problem. If it's repeatable, please send me your current project file.

Don
 
Hi,

Just tried it again with this project and it is doing the same thing. Attached. It uses the KSAN BGL file I posted earlier.
 

Attachments

8. When I use Delete Approach Lights for a MALSR approach that was created by using Use Stock Lights, the green Threshold Lights are not deleted.
 
Hi Tom. Re the archive you just sent, it does not contain any placement data, just stock data. That being the case, it's difficult to follow the sequence of operations you outlined above. But, if I start adding stock data, I can find no issue.

I have just posted 4.1.13. It doesn't change anything re clearing/entering data. What it does do in display imported undesignated taxiways with lights (only) on the specified side(s). What this new release fails to do is to connect sequential undesignated taxiways (like it does designated ones). So, for the moment, each link has starting and ending lights, creating a duplicate light at each intersection. There is a problem in the code for creating the image of connected taxiways that omits, or adds extraneous, links when processing undesignated links. I will resolve that, but it's a very complex area and, so, may take a day or so.

As far as I can tell, this new release addresses all the issues you've raised save for the threshold lights issue. If it doesn't, please jog my memory. To address the possibility of confusion, I have changed references to the red/green lights at the runways thresholds from "Threshold Lights Bar" to "Runway End Lights". Several posts above, it appears you intended to add a Dark/Green threshold light bar. Such a line of lights would not be considered part of the Approach Lights - regardless of your intent in placing them there. They would be manipulated by the newly-named Runway End Lights functions.

Don
 
Hi,

Yes, there is no placement data at all in this airport - it's a brand new project before I have placed any lights. I do not apply Use Stock Lights in this case - I am adding lights from scratch. I cannot determine how much time applying Use Stock Lights and then fixing all the issues vs doing them from scratch will take until I try both approaches myself. That way I can use the most efficient method.

Re: the approach issue in the display, I will try to detail what I do (and is still a problem in 4.1.13):

1. Load the project I sent you.
2. Click the runway to select it.
aflt_ksan_approach_finish.jpg


3. Right click and choose Add/Edit Approach Lights:

aflt_ksan_approach_add.jpg


4. In the box that appears, choose MALSR and click Place Lights.
5. Right click the selected runway and select Delete Approach Lights:

aflt_ksan_approach_delete.jpg


6. Click OK at the deletion confirmation box.
7. Select and right click the runway and choose Add/Edit Approach Lights:

aflt_ksan_approach_add.jpg


8. In the box that appears, choose MALSR and click Place Lights.
9. The approach does not display on the map.

aflt_ksan_approach_finish.jpg


If the approach lights appear the second time, repeat this process - delete the approach lights and try to re-add them.
 
Last edited:
Re: the threshold lights. What I wanted to do was to create a line of little 3D spotlights that shined away from the runway. This 3D model is used on the approach stands, and only shines in one direction. This is what is created from my KSAN ADE file applying Use Stock Lights and I wanted to be able to duplicate that without applying Use Stock Lights. As I said, this I was able to do by creating a MALSR approach for that end of the runway and then deleting the centerline approach stands (or just unchecking that Centerline box in the approach builder dialog).

I did not want to use the 3D model of the taxiway/runway edge lights, as used in the Runway End Lights. I wanted to use the little spotlights as used on the approach dialog (type = Approach)- i.e. as when you specify Threshold lights in the MALSR dialog box. This issue is solved.
 
Last edited:
These issues still appear to be present in 4.1.13, the first two you mention in your post above:

1. Use Stock Lights creates duplicate lights on undesignated taxiways.
2. Use Stock Lights creates lights on the taxiway surface at the junction of designated and undesignated taxiways, as well as the junction between undesignated taxiways.
3. Use Stock Lights with a MALSR approach with no strobes in the ADE file ends up with 5 strobes in AFLT.
5. The taxiway and runway lights are pulsing, but only when facing 270 (at KSAN), not when facing 090. It is about every 11 seconds on my machine.

Getting closer!

Hope this helps,
 
Last edited:
Yes, there is no placement data at all in this airport - it's a brand new project before I have placed any lights. I do not apply Use Stock Lights in this case - I am adding lights from scratch. I cannot determine how much time applying Use Stock Lights and then fixing all the issues vs doing them from scratch will take until I try both approaches myself. That way I can use the most efficient method.
Sometimes I just need to be led by the hand. (I missed the create/delete/create again sequence. I can now duplicate the issue.

These issues still appear to be present in 4.1.13, the first two you mention in your post above:

1. Use Stock Lights creates duplicate lights on undesignated taxiways.
I wonder if we still mean the same thing by duplicate lights. As I noted earlier, the lights at the start of one segment do still overlap the ones at the end of the previous sequential segment. But, I no longer get whole lines of lights duplicated as before. Are you?.

2. Use Stock Lights creates lights on the taxiway surface at the junction of designated and undesignated taxiways, as well as the junction between undesignated taxiways.
Yes. But there's little I can do about it other than delete the light. In real life, however, I suspect the light would be placed at an edge nearby, but I have no way of knowing where it should go and, if I delete it and its needed, you'd have to enter another. I felt that doing nothing and let the user decide was the best approach (but perhaps you can convince me otherwise). This likely will be significantly improved once I finish the current rework.

3. Use Stock Lights with a MALSR approach with no strobes in the ADE file ends up with 5 strobes in AFLT.
That one I did forget about. Next release

5. The taxiway and runway lights are pulsing, but only when facing 270 (at KSAN), not when facing 090. It is about every 11 seconds on my machine.
Yes. It's on my list (which is getting shorter) but near the bottom since its not stopping progress. I've got to finish the rework of the outlining of undesignated links first.

Thanks
Don
 
Back
Top