Products Support > Honolulu FSX/P3D
Disappearing AI in Honolulu FSX
virtuali:
--- Quote from: petakas on December 16, 2013, 11:22:10 pm ---Unfortunately I am not able to have an AI library with newer models only like many other simmers.
--- End quote ---
Then you will have to miss those specific models.
--- Quote ---Still what you ask us the users (to change AI models) nobody of other equally excellent of your level designers (FlyTampa, FSDG, 29Palms) has asked us and still they have made Excellent sceneries, WITH old AI visible and NOT heavy due to their code.
--- End quote ---
That's because they haven't used custom runways for such airports. The problem happens only with the COMBINATION of using an airport with custom runway textures and legacy AI models. And no, it's not an "FSDT thing", many airports from Aerosoft are made in the same way.
But this is something we solved in later sceneries, not just JFK2, but KDFW, KLAX and CYVR also have fully custom runways, but without requiring native AI models. However, it doesn't change the fact that, even if you CAN use FS8 AI models on such airports, it wouldn't be a very good idea using them anyway, because one a scenery is entirely 100% native FSX code, having FS8 code mixed in is really bad for performances, but you won't notice it if the scenery is not made like that.
--- Quote ---You made it with JFK v2 why not try it for PHNL ?
--- End quote ---
Because what we did with JFK2 was a complete remake of the airport, which was a PAID upgrade but, of course, it wasn't "just" to be compatible with legacy AI, it was to update the airport that had a major overhaul, to be fully compatible with DX10/11, etc.
--- Quote ---Please reconsider, you have done it in KFK v2, is it impossible for PHNL ?
--- End quote ---
There's nothing to "reconsider", it's fairly obvious that, whenever we'll decide to revisit a scenery for a remake, it will be done using fully native code. Again, not for allowing you to use outdated AIs, but to improve the scenery with such code, and entirely unrelated to the AI.
--- Quote ---These missing AI's are really degrading the whole immersion factor and disabling aircraft shadows (to show older AI) is a serious cut back in realism
--- End quote ---
No, you are ONLY missing the small percentage of your AIs that haven't been updated to FSX code. I really hope that, for your own fps sake, those are a minority of your AI collection.
--- Quote ---Also in any change to Graphics options FSX reverts resolution back to 1024 (from 4096 that some of our aircraft/sceneries/clouds need).
--- End quote ---
That's not correct. In fact, one of the main advantage of having the Addon Manager setting up the textures resolution, is that you CAN change your graphic settings as you please, but the texture resolution will STAY at the value set with the Addon Manager because the Addon Manager, opposite to what other similar utilities, does NOT "just" set the 4096 value in the FSX.CFG, but it will ALSO set the value in memory, calling an FSX API routine that will set that value AS IF FSX was restarted.
This means, even if you change anything in the settings, you can use the Addon Manager to set the textures resolution back to 4096, without restarting.
AirBorne:
I think this is so annoying disabling the shadows without consent of the simmer. I'd like to suggest that you make it optional.
For now, I solved this issue creating a .BAT file that every time FSX is started up a new custom FSX.CFG is put, and the previous one deleted.
virtuali:
--- Quote from: AirBorne on December 27, 2014, 11:00:30 pm ---I think this is so annoying disabling the shadows without consent of the simmer. I'd like to suggest that you make it optional.
--- End quote ---
I think you are confusing the automatic switching of airplane shadows depending on altitude that happens ONLY inside of the area of an FSDT scenery, with the suggestion to turn if off when using LEGACY AI models that has been discussed here.
The Addon Manager DOES NOT disable shadows "without consent", it controls AI shadows to be on/off depending on the altitude, and ONLY when you are flying inside an area of an FSDT scenery, but your original setting in the FSX.CFG is preserved and restored once you exit from the area.
This switch is NOT made in order to fix compatibility with legacy AI models, it's made because, with our latest sceneries ( those with full DX10 compatibility and 100% native FSX code ), the ground textures are NOT compatible with airplane shadows.
Over a certain altitude, you WON'T SEE THE SHADOW ANYWAY so, it's totally useless to keep it on, losing performances, because FSX is still trying to draw the shadow, but you won't be able to see it due to how the ground scenery has been made in order to be fully DX10 compatible and fully FSX native, with all the performance benefit that comes with it, like the memory saving you can achieve with DX10 and the net 30% fps increase that a scenery for, let's say, JFK, gained when switching to native FSX code.
If we made the airplane shadows "optional", as you are suggesting here, you would likely see a performance decrease with NO visual benefits whatsoever, because even if you had the airplane shadows enabled, they won't be visible, but they would still cause an fps loss, which would be higher the more AI you have.
So, when flying over an area of an FSDT scenery, if you had the airplane shadows enabled under your control, you wouldn't see the shadows over a certain altitude, but you would still have the performance loss associated with it, THAT'S why that setting is not "optional".
If you *knew* about this (now you know...), you would probably complain that is "annoying" having to constantly remind to turn OFF airplane shadows (that you wouldn't be able to see) on an FSDT scenery to get the best possible performances, and how it would be better if it were "automatic", which is exactly how it is right now.
When you are OUTSIDE the area of an FSDT scenery, the setting is restored as it were, and it's BACK under YOUR control.
--- Quote ---For now, I solved this issue creating a .BAT file that every time FSX is started up a new custom FSX.CFG is put, and the previous one deleted.
--- End quote ---
Totally useless, because outside of an area of an FSDT scenery, the setting will be restored as it was before, and when inside an area of an FSDT scenery, the shadow will go on/off depending on the altitude regardless of what's inside the FSX.CFG, because it will be changed directly in the FSX memory.
Restoring the FSX.CFG would help only in these two cases:
1) You ended a flight when flying over an FSDT scenery on an higher altitude than the threshold where the shadows would be switched off.
2) You saved a startup flight over an FSDT scenery on an higher altitude than the threshold where the shadows would be switched off.
So no, the shadows switching depending on altitude inside the area of an FSDT scenery will not made optional, but we might change the Addon Manager that your original setting would be restored also when exiting from FSX when you are flying over an FSDT scenery, that's the only thing that would be useful.
AirBorne:
What annoys me is the fact that occasionally I get the shadows disabled "forever" I don't know why and how, that's why I created the batch file. And I don't use to quit FSX while flying (at such amount of altitude), rather, I use to save the flight after getting into the gate, running shutdown checklist, etc, and just then I quit FSX...
virtuali:
--- Quote from: AirBorne on December 31, 2014, 05:11:07 am ---What annoys me is the fact that occasionally I get the shadows disabled "forever" I don't know why and how, that's why I created the batch file.
--- End quote ---
As I've said, your airplane shadows would be disabled permanently in the following cases:
- You ended the flight when the airplane was over an FSDT scenery at an higher altitude than the shadow-cutting threshold altitude for that scenery.
- You saved a startup flight over an FSDT scenery, in air.
- FSX crashed, so it couldn't save the updated FSX.CFG. If FSX crashes, any changes made to the FSX.CFG won't be saved.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version