-
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.
Just beginning
- Thread starter SubLogical
- Start date
- Messages
- 115
- Country
Thanks Don,
That's far too obvious for my mind ... I'm always looking for the complicated solutions!
Appreciated.
Ken
That's far too obvious for my mind ... I'm always looking for the complicated solutions!
Appreciated.
Ken
- Messages
- 34,981
- Country
ADE has an undo - if that does not work (or is not available) for some things then why not make a safe copy of the project file before trying. Also you can play around with a project and not save it or save it under a new name.
- Messages
- 115
- Country
Don was right to suggest saving the file and then making the changes which I did. I hadn't had Jon's advice then to save the pre-change file "out of the save loop" so it has been subsequently overwritten.
However, after reviewing the manual options of "editing the stock edition" or "creating a new version with the hide the old" feature I thought the latter would produce the cleanest result and went for it.
I clicked Go at the "choice warning" and the new ILS icon appeared at the end of the runway and the glide slope icon at the beginning ... all without any fuss which suggested to me it went well. I thought in a misfire I could always re-load the BGL file and struggle on. But if it worked, it worked well and I must say the thought behind the orphanizing was extremely clever.
So I guess we'll know how well it worked when the time comes to boot it up, but one thing is for sure I wasn't going on without the additions mentioned.
jvile, I never had any intentions of adding back the stock ILS file ... I was planning to add the GS and VOR/DME for this airport which has changed a lot since the original build in 2004. I wasn't sure if that could be accomplished by retaining the stock ILS and also there has been a 2000 ft runway extension recently which may have affected the location of the original.
Many thanks for all the interest.
Ken
However, after reviewing the manual options of "editing the stock edition" or "creating a new version with the hide the old" feature I thought the latter would produce the cleanest result and went for it.
I clicked Go at the "choice warning" and the new ILS icon appeared at the end of the runway and the glide slope icon at the beginning ... all without any fuss which suggested to me it went well. I thought in a misfire I could always re-load the BGL file and struggle on. But if it worked, it worked well and I must say the thought behind the orphanizing was extremely clever.
So I guess we'll know how well it worked when the time comes to boot it up, but one thing is for sure I wasn't going on without the additions mentioned.
jvile, I never had any intentions of adding back the stock ILS file ... I was planning to add the GS and VOR/DME for this airport which has changed a lot since the original build in 2004. I wasn't sure if that could be accomplished by retaining the stock ILS and also there has been a 2000 ft runway extension recently which may have affected the location of the original.
Many thanks for all the interest.
Ken
tgibson
Resource contributor
- Messages
- 11,801
- Country
You are doing exactly the same thing both ways, but the chances of ending up with a corrupted file is much greater if you delete and then add back. Editing the existing ILS is *by far* the cleaner way to do this.
In fact, if ADE allows editing an object that is always the best way to do it. Only when ADE will not edit an object (a terrain polygon, for example) do you need to delete or exclude it, and then create a new one.
In fact, if ADE allows editing an object that is always the best way to do it. Only when ADE will not edit an object (a terrain polygon, for example) do you need to delete or exclude it, and then create a new one.
- Messages
- 115
- Country
Morning Tom,
Well doubtless you have the advantage on me in facing that kind of situation but I was impressed by the cautionary note in the manual regarding editing a stock ILS which reads "Note, that you are warned, that this is an ILS from Stock" whereas the "orphanizing " struck me as the cleanest option with the least indications of likely trouble. But you can see in my earlier post before the dastardly deed was committed that I had reservations about which way to jump.
Perhaps the proof will be in the pudding ... since each alternative seems to have it's own risks ... I guess we won't know till I get to the point of learning how to compile and run it in FS.
On the positive side I'm having a ball ... enjoying the learning curve and seemingly making progress. The snow is going and we'll be opening the ranch by the end of the month which means I'll have to put my toys away and get back to the 24/7 ... so I'm pushing this project along with great hopes!
Well doubtless you have the advantage on me in facing that kind of situation but I was impressed by the cautionary note in the manual regarding editing a stock ILS which reads "Note, that you are warned, that this is an ILS from Stock" whereas the "orphanizing " struck me as the cleanest option with the least indications of likely trouble. But you can see in my earlier post before the dastardly deed was committed that I had reservations about which way to jump.
Perhaps the proof will be in the pudding ... since each alternative seems to have it's own risks ... I guess we won't know till I get to the point of learning how to compile and run it in FS.
On the positive side I'm having a ball ... enjoying the learning curve and seemingly making progress. The snow is going and we'll be opening the ranch by the end of the month which means I'll have to put my toys away and get back to the 24/7 ... so I'm pushing this project along with great hopes!
- Messages
- 8,893
My preference is
Add the 2000 ft to the runway
Drag the Localizer Symbol (big green triangle) to the end of the extended runway
In the property window of the Localizer check GS and DME. ADE will add those.
Drag the GS (small green triangle) to the proper place along side the runway
Drag the DME square to either the beginning on end of runway.
Reposition the Start Location
- Messages
- 115
- Country
Jim ..... now you tell me! That looks like a piece of cake and trouble free. I had already re-sized the rwy and interestingly the ILS icon went with it.
I was uncertain of the ability to safely edit the existing ILS ... and it never occurred to me that it would be as simple as ticking the edit ILS boxes. Let's just say I'm a lot smarter this morning than I was yesterday.
The real question is whether I got away with it but I'm pretty certain ADE wouldn't have created the orphan option if it was a path to a file corruption. I wonder now though whether the orphan method was mean't just for removing (and not replacing) the ILS.
Ken
I was uncertain of the ability to safely edit the existing ILS ... and it never occurred to me that it would be as simple as ticking the edit ILS boxes. Let's just say I'm a lot smarter this morning than I was yesterday.
The real question is whether I got away with it but I'm pretty certain ADE wouldn't have created the orphan option if it was a path to a file corruption. I wonder now though whether the orphan method was mean't just for removing (and not replacing) the ILS.
Ken
- Messages
- 115
- Country
Honesty is the best policy according to mother but in this case it comes with some interesting results and a truckload of embarrassment. My added ILS. GS and DME did not remove the Stock ILS which was hard to see since they covered each other. So with trepidation I retained the Stock ILS, added the GS and DME and deleted my added version.
But I guess it raises the question of why ADE did not send the stock north.
Just to thank Jim, I was then able to do exactly as he suggested. Now seems to be a good time to get this effort compiled and start seeing exactly how I'm doing.
Sorry for all the confusion but that's what happens when you let a newbie in the door ... !
Ken
But I guess it raises the question of why ADE did not send the stock north.
Just to thank Jim, I was then able to do exactly as he suggested. Now seems to be a good time to get this effort compiled and start seeing exactly how I'm doing.
Sorry for all the confusion but that's what happens when you let a newbie in the door ... !
Ken