FSDreamTeam forum
Products Support => Los Angeles support FSX/P3D => Topic started by: Tom340 on April 18, 2020, 05:32:40 pm
-
Hi, I think I found a bug on this scenery when you almost fly over the runway 25L thresold.... You can see the floating highway!
-
Hi, I think I found a bug on this scenery when you almost fly over the runway 25L thresold.... You can see the floating highway!
Same here. The highway "takes-off" and "lands" back again on the ground depending on your position and where are you looking for
-
Tried that, but I cannot reproduce it:
Have you done a similar kind of approach ? I tried rotating the view a bit, but can't see the problem.
-
Tried that, but I cannot reproduce it:
Have you done a similar kind of approach ? I tried rotating the view a bit, but can't see the problem.
Hi Umberto, may I ask you what are your mesh resolution settings? By the way, I have also installed ORBX Global Base and OpenLC North America....
-
Same issue here. https://imgur.com/a/uHxMMfd
-
I remember seeing that before as well, but haven't since updating to the most recent 5.1 HF1.
-
I remember seeing that before as well, but haven't since updating to the most recent 5.1 HF1.
I'm on 5.1/HF1 as well
-
As I've said, I'm not able to reproduce it:
-
As I've said, I'm not able to reproduce it:
Do you have any suggestions on where I can start to try reproducing it myself? What settings, scenery conflicts, etc. could be causing this?
-
You might start with resetting your shaders, by removing this folder:
%LOCALAPPDATA%\Lockheed Martin\Prepar3d v5\Shaders
They will be recreated on the next startup, sometimes it fixes graphic issues. If that doesn't fix it, you might try resetting all your settings to default, by running the "Delete Generated Files" command in the P3D root.
This will reset all settings to default, so you'll likely see many questions about re-enabling your add-ons on the next start, at least the ones with their add-on.xml in the Documents folders, but you might have to reinstall\reconfigure those that don't or don't even use the add-on.xml method at all.
-
I'm also having the same issue. A popular youtuber (The Flight Simmer) has encountered it as well. I think FSDT should look more into it at this point.
-
I'm also having the same issue. A popular youtuber (The Flight Simmer) has encountered it as well. I think FSDT should look more into it at this point.
That only means both you and that popular youtuber must have the same problem, which cannot be replicated on a clean install, which is the only possible way to know for sure if the scenery itself has a problem, or it's something else that has been installed that is causing it, or some non-standard tweak, or anything else that is not related to the scenery.
I already indicated two different solutions:
- resetting the shaders
- temporarily disable every add-on, and see if the problem happens with nothing else installed, and re-enable them one by one, until you find the conflict.
-
I'm also having the same issue. A popular youtuber (The Flight Simmer) has encountered it as well. I think FSDT should look more into it at this point.
That only means both you and that popular youtuber must have the same problem
Actually I'm having the same problem on a fresh install of P3Dv5 as well.
-
Actually I'm having the same problem on a fresh install of P3Dv5 as well.
As I've said, I cannot reproduce it ( and I posted a video about it), there must be something different, maybe in your graphic settings, tweaks, etc. If you could post your graphic setting in P3D 5 ( which version *exactly* ), I might try to reproduce it with those.
-
I am also having this issue. Definitely a FSDT problem. See attached images below.
https://imgur.com/SzViEuW
https://imgur.com/WyKtjBU
-
I am also having this issue. Definitely a FSDT problem.
As I've said, I cannot reproduce it ( and I posted a video about it), there must be something different, maybe in your graphic settings, tweaks, etc. If you could post your graphic setting in P3D 5 ( which version *exactly* ), I might try to reproduce it with those.
-
Same problem here, when moving with chaseplane over the road at some point it will appear normal, moving a bit further it goes up again...
Do you have serious testers?? I really doubt so... P3D V5 Versions seem to be super buggy...
LAX - floating road
CLT - (non existent) Night"lighting"
IAH - Transmittiontowers on the apron
JFK - Airport eqipment on taxiways
DFW - Dont we all love looking out the cockpit during bright daylight and enjoy pitch black groundtextures at the gates?
GSX - AI detection / GSX crashing often enough / Vehicles run into each other + User Vehicle / still no textures / Dude still tries to convince me I shouldnt start engines at 0°C weather and sunshine (I must have done hundreds of pushbacks myself, unless there was heavy snowfall I NEVER waited until push was complete to give the engines clear...)
And I am not even gonna start on the AFCAD positoning, blurry ground textures and dynamic lighting. Great to have some decent freeware around, sad to need to reinstall every time liveupdater runs (to be fair, not on the AFCADs).
Thanks for the unreproducable support :D
-
Same problem here, when moving with chaseplane over the road at some point it will appear normal, moving a bit further it goes up again...
Does your sentence "when moving with chaseplane" means it doesn't happen if you don't use it ?
Do you have serious testers?? I really doubt so... P3D V5 Versions seem to be super buggy...
I don't know what you are trying to say here. Do you find P3D V5 *itself* to be as bug-free as P3D 4.5 ever was ? We made sceneries that are compliant with the P3D SDK, which work flawlessly in P3D4 it's not as if we programmed the road at KLAX to be in the air, do you really believe that ?
Don't you recall one terminal at KORD V2 which floated in the air ? It was a P3D bug, and it wax FIXED in an Hotfix, we managed to do a temporary workaround but, in that case, we *were* able to reproduce it at least. But it was really fixed by LM.
LAX - floating road
Cannot be reproduced
CLT - (non existent) Night"lighting"
The problem here is opposite of what you might think. We checked users reports, and realized we had MORE night lights than there are in real life, since in real life most taxiways don't have any lights, but we have those in the scenery. So, we are a bit stuck here because, users reported taxiway lights as "missing" ( because they are "missing" in a sector ) but, if we really had to do a proper fix that would match reality, we would have to REMOVE taillights even further so, users would then complain we made the fix worse...
IAH - Transmittiontowers on the apron
JFK - Airport eqipment on taxiways
Neither of these are happening here.
However, it will surely happen if you refused to upgrade the AFCAD when the Live Update prompted to do that because, since the the default scenery in P3DV5 changed, we had to update ALL our AFCADs to exclude default objects by taking into account the different default scenery.
But if you kept your modified AFCAD, you must redo the Exclusion zones yourself.
DFW - Dont we all love looking out the cockpit during bright daylight and enjoy pitch black groundtextures at the gates?
GSX - AI detection
Which work just fine, but I must admit we tested only these two cases:
- Default AI
- Ultimate Traffic Live 2, to ensure GSX works with AI traffic generated programmatically with Simconnect.
I'm sorry, but it's impossible for us to test all the possible strange combinations of multiple freeware products that users have.
GSX crashing often enough
If you think GSX is "crashing" ( a GSX crash is when you see an error log from GSX ), then please provide a PROPER error report, with your error log and, when this is done, we ALWAYS fix that crash, because THAT one IS a "GSX crash".
If you think GSX caused a crash to the sim, it hasn't.
There's a known bug in P3D V5 Html menu, which results in the menu being stuck, and the clear proof it's not GSX fault is that it happens with the default ATC menu as well and it's not fixed by restarting Couatl ( the simulator itself is stuck ).
And there's another known bug that, if you revert to the previous Scaleform menu, the sim *can* crash with a VCRUNTIME.DLL error, randomly, when you open the menu several times, and the clear proof it's not GSX fault is this ALSO happens with the default ATC menu as well.
Vehicles run into each other
This has been explained so many times: vehicles are not really "aware" of each other, because doing that will open a whole new kind of problem that would be even more annoying of vehicles HARMLESSLY "crashing" into each other, that would be vehicles STUCK, yielding to each other so, we obviously chose not try to do that, and instead relying on either customizing the start positions OR users calling services in a sensible way. If you are using automatic servicing, this might happen more frequently, because you lose the ability to prevent vehicle clashing into each other if you let the services running automatically, this was an option we added because users asked for it, but I think it's best to call all services separately.
User Vehicle / still no textures
You mean lack of DirectX 12 support ?
This has been explained so many times as well: we are not going to try to convert our DirectX 11 code into Direct X 12, it's just too dangerous ( see how much issue TrueGlass caused in V5, I'm not even sure all the DXGI crashes were fixed ), and we always put reliability before anything else, but that's not the only reason.
We made heavy use of True Type Fonts as well, which required DirectWrite, which is an API that has been REMOVED from DX12, and because of this we decided to just move away from DX12, since P3D 5.1 added a new kind of Render to Texture method, based on Html5. However, is still missing features we need, like support for non-square textures ( ALL GSX textures are non-square ) and support for higher resolutions, which we reported to LM hoping both will come in a future update of the sim.
/ Dude still tries to convince me I shouldnt start engines at 0°C weather and sunshine(I must have done hundreds of pushbacks myself, unless there was heavy snowfall I NEVER waited until push was complete to give the engines clear...)
This must be airline or airport dependent, because we have been asked by users that work on ground handling, that turning on engines in slipper conditions might be dangerous for the towbar. You are making it look as a "bug", when should have been obviously clear this was made intentionally. So yes, we might add another OPTION to disable it.
And I am not even gonna start on the AFCAD positoning
I really don't know what you are referring to here. This is the KLAX forum, are you referring to AFCAD positioning at KLAX ? That would be an example of the most possible precise positioning we ever made, because each and every parking has been carefully tweaked to work together with the GSX customization.
If you are referring to other airports, then please open a proper report with a proper example in those sceneries support sections.
, blurry ground textures and dynamic lighting.
Again, I don't know what you are referring to here. Are you referring to KLAX ? Assuming you are, KLAX has a ground resolution that was ( and still is ) perfectly fine when the scenery was made in 2011.
And, as explained so many times already, it REQUIRES to use 4K textures because, we haven't used 4K to do "ultra resolution", we used it to get more fps, which means we used the same overall resolution of other sceneries we made around that time but, instead of using many 1K textures, we used very few 4K texture. Moving up from 1K to 4K DECREASE the number of textures by 16x AT THE SAME resolution.
Which means, if you use 2K or even 1K textures, you are *downgrading* the scenery resolution to what is supposed to look like.
So, if due to the fact P3D V5 is at an higher risk of crashing when close to VRAM exhaustion, you decided to set it at 2K, it will look bad at KLAX because, of course, we couldn't possibly anticipate in 2011 that in 2021 a new sim would came out that would denied users from the ability to use 4K resolution that worked well EVEN IN FSX! And of course, we couldn't possibly anticipate that buying a video card with lots of VRAM would proved to be so difficult.
But at the same time, you cannot expect or demand we'd update a scenery we let you use FOR FREE in FS9, FSX, P3D 1 to 5 without ever charging for any updates ( yes, KLAX compatibility starts with FS9, and use the same license ), doing a very complex makeover to convert from few 4K textures to *many* 1K textures ( losing fps in the process, of course, since 16x more materials will affect fps ), just because a new sim is quite unreliable when lots of VRAM is used.
About the lack of dynamic lighting, I'll stress AGAIN KLAX it's a scenery that was made for FS9 and FSX, in 2011, and it features one of the BEST STATIC lighting out there, because obviously nobody could possibly anticipate something like DL in 2011, since it first came out with P3DV4 in 2017, so we obviously used it for our sceneries that came out *after* that date, like KCLT or KSDF or LFSB or KORD V2.
Retro-fitting KLAX for DL, which was a scenery *designed* for static lights, would be similar to redoing it from scratch, and it will be likely have a huge impact on fps, in an area that is ALREADY heavy on fps without even adding any add-ons so no, it doesn't make any sense right now, considering the airport itself is undergoing a big upgrade so yes, we'll likely redo KLAX in the next years, although we cannot possibly be sure in *which* simulator will work.
-
Does your sentence "when moving with chaseplane" means it doesn't happen if you don't use it ?
No, it also happens at the default cockpit view.
I don't know what you are trying to say here. Do you find P3D V5 *itself* to be as bug-free as P3D 4.5 ever was ? We made sceneries that are compliant with the P3D SDK, which work flawlessly in P3D4 it's not as if we programmed the road at KLAX to be in the air, do you really believe that ?
I dont, but according to the reports here it seems to be a common problem with several users but other the "cannot reproduce" there is no step towards us customers to try fixing it.
Don't you recall one terminal at KORD V2 which floated in the air ? It was a P3D bug, and it wax FIXED in an Hotfix, we managed to do a temporary workaround but, in that case, we *were* able to reproduce it at least. But it was really fixed by LM.
Dont plan to purchase KORD V2 unless it has working AI Jetways (incl my traffic). DDs KORD is a good substitution.
Cannot be reproduced
Did not expect any other answer from your side.
The problem here is opposite of what you might think. We checked users reports, and realized we had MORE night lights than there are in real life, since in real life most taxiways don't have any lights, but we have those in the scenery. So, we are a bit stuck here because, users reported taxiway lights as "missing" ( because they are "missing" in a sector ) but, if we really had to do a proper fix that would match reality, we would have to REMOVE taillights even further so, users would then complain we made the fix worse...
Let the pictures talk for CLT:
https://abload.de/img/clt125kcj.jpg (https://abload.de/img/clt125kcj.jpg)
https://abload.de/img/clt2cdjnz.jpg (https://abload.de/img/clt2cdjnz.jpg)
Airport is clearly overflowing with lights
Neither of these are happening here.
IAH:
https://abload.de/img/iah1czkp9.jpg (https://abload.de/img/iah1czkp9.jpg)
https://abload.de/img/iah2ark1q.jpg (https://abload.de/img/iah2ark1q.jpg)
JFK:
https://abload.de/img/jfk1qtjp3.jpg (https://abload.de/img/jfk1qtjp3.jpg)
https://abload.de/img/jfk20lkev.jpg (https://abload.de/img/jfk20lkev.jpg)
https://abload.de/img/jfk31hkdk.jpg (https://abload.de/img/jfk31hkdk.jpg)
However, it will surely happen if you refused to upgrade the AFCAD when the Live Update prompted to do that because, since the the default scenery in P3DV5 changed, we had to update ALL our AFCADs to exclude default objects by taking into account the different default scenery.
But if you kept your modified AFCAD, you must redo the Exclusion zones yourself.
Then please do it correctly for IAH because the transmitiontowers are there with your default AFCAD, the JFK vehicles clearly looks like FSDTs to me. (BTW why does every single scenery developer always place wrong ULDs with wrong logos and wrong ID at every airport? Is it too difficult?)
I'm sorry, but it's impossible for us to test all the possible strange combinations of multiple freeware products that users have.
I know, "can not reproduce".
If you think GSX is "crashing" ( a GSX crash is when you see an error log from GSX ), then please provide a PROPER error report, with your error log and, when this is done, we ALWAYS fix that crash, because THAT one IS a "GSX crash".
I mean it just hangs and does not react at all (not just the window, animations stop etc.). Can only be solved with -disable and -enable in the menu. Maybe a FSLabs connection problem.
This has been explained so many times: vehicles are not really "aware" of each other, because doing that will open a whole new kind of problem that would be even more annoying of vehicles HARMLESSLY "crashing" into each other, that would be vehicles STUCK, yielding to each other so, we obviously chose not try to do that, and instead relying on either customizing the start positions OR users calling services in a sensible way. If you are using automatic servicing, this might happen more frequently, because you lose the ability to prevent vehicle clashing into each other if you let the services running automatically, this was an option we added because users asked for it, but I think it's best to call all services separately.
I am not talking about different services but also the baggage vehicles are parked into each other on the smaller Busses while loading.
You mean lack of DirectX 12 support ?
This has been explained so many times as well: we are not going to try to convert our DirectX 11 code into Direct X 12, it's just too dangerous ( see how much issue TrueGlass caused in V5, I'm not even sure all the DXGI crashes were fixed ), and we always put reliability before anything else, but that's not the only reason.
We made heavy use of True Type Fonts as well, which required DirectWrite, which is an API that has been REMOVED from DX12, and because of this we decided to just move away from DX12, since P3D 5.1 added a new kind of Render to Texture method, based on Html5. However, is still missing features we need, like support for non-square textures ( ALL GSX textures are non-square ) and support for higher resolutions, which we reported to LM hoping both will come in a future update of the sim.
Im no programmer so cannot comment on that but if I am still wondering why I am able to spawn over 200 AI airplanes with indivdual textures without any trouble but having 5 vehicles show up with certain textures is impossible.
This must be airline or airport dependent, because we have been asked by users that work on ground handling, that turning on engines in slipper conditions might be dangerous for the towbar. You are making it look as a "bug", when should have been obviously clear this was made intentionally. So yes, we might add another OPTION to disable it.
Slippery yes but why does GSX asume it is slippery with -1°C and clear sunshine? There is no reason to wait unless there is some snow or ice buildup on the apron.
And by the way why is the first phrase at the pushback "Hello Captain, we are ready for pushback" when the tug is nowhere to be connected nor ready to push? There are Pilots (on some airlines at least) who will release the parking brake immediatly when you say that, so saying you are ready when you are clearly not is a big no-no!
I really don't know what you are referring to here. This is the KLAX forum, are you referring to AFCAD positioning at KLAX ? That would be an example of the most possible precise positioning we ever made, because each and every parking has been carefully tweaked to work together with the GSX customization.
If you are referring to other airports, then please open a proper report with a proper example in those sceneries support sections.
Again, I don't know what you are referring to here. Are you referring to KLAX ? Assuming you are, KLAX has a ground resolution that was ( and still is ) perfectly fine when the scenery was made in 2011. [...]
Hence the "And I am not even gonna start"
-
I want to install KLAX into P3Dv5 but I don't think the FSDT KLAX has an Installer for P3Dv5, does it?
Patricio
-
No, it also happens at the default cockpit view.
But since it doesn't happen here, and I also posted a video to prove it, it can only be caused by something else we haven't found yet, like a setting or a conflict with another add-on that must be triggering some kind of simulator bug that wasn't there in P3D V4.
I dont, but according to the reports here it seems to be a common problem with several users but other the "cannot reproduce" there is no step towards us customers to try fixing it.
We already took every step to check this but, if it's caused by a simulator bug ( like the floating building at KORD V2, which were fixed by LM without any change on our part ), there's not much we can do. And even if we wanted to find some workaround, we must be able to reproduce it first.
Dont plan to purchase KORD V2 unless it has working AI Jetways (incl my traffic). DDs KORD is a good substitution.
It looks like you are a bit out of touch of things: we have jetways working with AI since several months.
Did not expect any other answer from your side.
Again, I'm not sure what you are trying to say or imply here. I haven't posted another video, because it didn't seem to do much to satisfy you, like when I posted a video proving I cannot reproduce the floating stuff at KLAX.
Let the pictures talk for CLT:
Airport is clearly overflowing with lights
I don't understand you here. What's wrong with those pictures ? Doesn't look as good as KORD V2 DL ?. NOTHING looks good as KORD V2 DL, because that's a scenery that was made for P3D/PBR, while KCLT is still a scenery compatible with FSX, so it's not designed for DL from the start.
And again, it would have been best if you were a bit more clear about that DL problem you are referring to. Too many lights ? Too few ?
And, if you read my reply, I was discussing about taxiway lights only: we realized we have MORE then the real airport has.
IAH:
JFK:
This, couples with your snarky "Did not expect any other answer from your side", seems to indicate you keep missing the point of my replies: it's not as if I don't BELIEVE it's happening TO YOU so no, there's no need to provide screenshots as "proof" this is happening TO YOU. I BELIEVE this is happening TO YOU.
What I'm trying to say is, this is a problem of the scenery itself, and it's NOT happening to anybody else, since right now you are the one and only that reported it.
Then please do it correctly for IAH because the transmitiontowers are there with your default AFCAD, the JFK vehicles clearly looks like FSDTs to me.
I can only repeat and confirm this is NOT happening without our default AFCAD so, if you haven't modified it, they are coming from ANOTHER AFCAD in conflict. Most common cause of conflicts are AFCAD from AI Traffic products which should be disabled if you have an add-on.
Note that, I'm ONLY referring to KIAH transmission towers, since I don't see anything "wrong" with JFK ULD placements, those were clearly intentional and, if you are trying to say that if we'd ever remade JFK in the future, we MIGHT place detail stuff a bit better than what we did in 2012 when JFK V2 came out, we probably will. But nothing in your screenshot of JFK ever indicates a "bug".
I mean it just hangs and does not react at all (not just the window, animations stop etc.). Can only be solved with -disable and -enable in the menu. Maybe a FSLabs connection problem.
First, you are using the wrong method to restart GSX, the correct one is "Restart Couatl" ( also suggested in the manual ). And, as explained so many times, if you *suspect* a GSX problem when used together with some airplane, ALWAYS test with an airplane that doesn't integrate with GSX first, before assuming the problem is GSX.
I am not talking about different services but also the baggage vehicles are parked into each other on the smaller Busses while loading.
Do you mean there's not enough space on A318/319 for both loaders ? That's precisely why GSX lets you to configure an airplane and, for example, disable a loader if that clash is really so difficult to bear for you.
Im no programmer so cannot comment on that but if I am still wondering why I am able to spawn over 200 AI airplanes with indivdual textures without any trouble but having 5 vehicles show up with certain textures is impossible.
"without any trouble" ? With P3D5 VRAM issues ? Look, I know that other developers, in order to sell products just don't care about stability or optimization but, the WHOLE point of using DirectX 11 in P3D V4 was to:
- Make extremely easy for users to create custom logos and repaints, by associating a base color theme and pick a .PNG image for the logo, all without even restarting the sim or GSX. Can you do that with your favorite AI product ? Are you able to create a custom repaint on the fly ?
- Optimize the program, the memory used AND the simulator startup time. Do you even know how AI work ? They create multiple variations of Simobjects so, for example, if you have 100 AI models and 200 airlines, they would add 20.000 ( yes 20 thousand ) NEW Simobjects to the sim. Their list is always kept in memory, and it's checked EVERY time is needed so, with 20K more Simobjects, your simulator startup time will increase dramatically, and when you browse to change the airplane, it will be very slow.
THIS is what we FIXED with DirectX 11 in P3D V4, GSX in FSX DOES use the gazilion-liveries method "just like AI packs" and yes, it has about 8000 MORE objects than the P3D version AND they cannot customized so easily, because to create a custom operator in GSX required a lot of manual work to create all these extra liveries folders and fallbacks for EACH GSX vehicle, and each time we added a new one, you'll had to redo all your repaints, since new vehicles broke the default repaint system, which was the only thing we could use in FSX ( or P3D before V4 ), lacking Render To Texture DirectX support.
So yes, while we COULD in theory switch back to the FSX method for P3D V5 but, are you sure it's really a good idea to add ANOTHER 8K Simobjects variation to a sim that I'm sure already contains thousands of AI variations AND lose the easy customization granted by Render To Texture ?
So no, the correct way is, of course, the one we chose to use, which is:
- Don't even try with DirectX 12, which in any case lacks features we used and we need from DirectX 11 ( no idea why MS removed DirectWrite from DX 12, their suggest using a special DX11-DX12 bridge which, of course, takes up EXTRA VRAM, something we just don't have in V5 ) and it's still not 100% reliable, see other developers issues with it.
- Wait for the new Render to Texture made in HTML5 to mature, which will likely fix all the issues, without having to resort to the FSX method of adding thousands of multi-liveries variations, which is clumsly, inflexible and slows down the sim too much.
Slippery yes but why does GSX asume it is slippery with -1°C and clear sunshine? There is no reason to wait unless there is some snow or ice buildup on the apron.
And again, this has been explained so many times and yes, it's not a GSX problem, it's the result of Metar arriving from Simconnect with wrong data or not arriving at all, and Metar is used to read the Dew point, and Dew point is used to estimate possible icing.
When Metar is not received or contains corrupted or missing data, and this has been observed mostly when using 3rd party weather engines, GSX reverts to the "simple" strategy of checking JUST the outside temperature, and since it's not possible to get the Dew point from the sim other than the metar ( there's no Simconnect variable for it ), with the simplified strategy, the slippery conditions are not detected as reliably as when we DO have proper Metar reports, which is the NORMAL case.
-
I want to install KLAX into P3Dv5 but I don't think the FSDT KLAX has an Installer for P3Dv5, does it?
Of course it does. The current installer for FSX support P3D too.
-
But since it doesn't happen here, and I also posted a video to prove it, it can only be caused by something else we haven't found yet, like a setting or a conflict with another add-on that must be triggering some kind of simulator bug that wasn't there in P3D V4.
So you keep looking for a solution? Because "Can not reproduce" sure does not sound like it.
It looks like you are a bit out of touch of things: we have jetways working with AI since several months.
Not with the way I get my AI Traffic injected.
I don't understand you here. What's wrong with those pictures ? Doesn't look as good as KORD V2 DL ?. NOTHING looks good as KORD V2 DL, because that's a scenery that was made for P3D/PBR, while KCLT is still a scenery compatible with FSX, so it's not designed for DL from the start.
And again, it would have been best if you were a bit more clear about that DL problem you are referring to. Too many lights ? Too few ?
And, if you read my reply, I was discussing about taxiway lights only: we realized we have MORE then the real airport has.
Im not talking about the lights but about the lighting. The apron is pitch black. And again, I do not own KORD V2 for several reasons so I cannot compare.
This, couples with your snarky "Did not expect any other answer from your side", seems to indicate you keep missing the point of my replies: it's not as if I don't BELIEVE it's happening TO YOU so no, there's no need to provide screenshots as "proof" this is happening TO YOU. I BELIEVE this is happening TO YOU.
What I'm trying to say is, this is a problem of the scenery itself, and it's NOT happening to anybody else, since right now you are the one and only that reported it.
So these guys (http://www.fsdreamteam.com/forum/index.php/topic,23500.0.html) are nobody?
I can only repeat and confirm this is NOT happening without our default AFCAD so, if you haven't modified it, they are coming from ANOTHER AFCAD in conflict. Most common cause of conflicts are AFCAD from AI Traffic products which should be disabled if you have an add-on.
Those pictures were taken with the default AFCAD, no other airport scenery anywhere near, I am not using any AI program coming with AFCADS. Speaking if KIAH AFCAD, have you tried a GSX pushback from gate C19? Position is "connected" with the wrong taxiway and it takes you through the taxiway lighting
Note that, I'm ONLY referring to KIAH transmission towers, since I don't see anything "wrong" with JFK ULD placements, those were clearly intentional and, if you are trying to say that if we'd ever remade JFK in the future, we MIGHT place detail stuff a bit better than what we did in 2012 when JFK V2 came out, we probably will. But nothing in your screenshot of JFK ever indicates a "bug".
So blocking of an entire taxiway is FSDTs standard (at least back then)? You can even see the ground equipment on your preview screenshots.
First, you are using the wrong method to restart GSX, the correct one is "Restart Couatl" ( also suggested in the manual ). And, as explained so many times, if you *suspect* a GSX problem when used together with some airplane, ALWAYS test with an airplane that doesn't integrate with GSX first, before assuming the problem is GSX.
Will try this the next time it happens
"without any trouble" ? With P3D5 VRAM issues ? Look, I know that other developers, in order to sell products just don't care about stability or optimization but, the WHOLE point of using DirectX 11 in P3D V4 was to:
- Make extremely easy for users to create custom logos and repaints, by associating a base color theme and pick a .PNG image for the logo, all without even restarting the sim or GSX. Can you do that with your favorite AI product ? Are you able to create a custom repaint on the fly ?
- Optimize the program, the memory used AND the simulator startup time. Do you even know how AI work ? They create multiple variations of Simobjects so, for example, if you have 100 AI models and 200 airlines, they would add 20.000 ( yes 20 thousand ) NEW Simobjects to the sim. Their list is always kept in memory, and it's checked EVERY time is needed so, with 20K more Simobjects, your simulator startup time will increase dramatically, and when you browse to change the airplane, it will be very slow.
Yes, without any trouble, at the moment I have 151 different Aircraft types (not including engine subtypes) and 535 different airlines resulting in 2357 individual repaints. My startup time is exactly 1 Minute to the main menu of P3D V5 and it takes 43 sekonds to load the scenario. With max. AI the VRAM usage is increasing by less than 1GB.
So yes, while we COULD in theory switch back to the FSX method for P3D V5 but, are you sure it's really a good idea to add ANOTHER 8K Simobjects variation to a sim that I'm sure already contains thousands of AI variations AND lose the easy customization granted by Render To Texture ?
I dont know, I have no chance of trying. But then in the US I need exactly 1 handling company for my airline because groundhandling is usually done inhouse there. In Europe you have only have maybe 2-3 different handling companies on a single airport, a few of them you will see at many airports so with (wild guess) about a dozen individual handling textures you get about 90% of westerneurope covered.
And again, this has been explained so many times and yes, it's not a GSX problem, it's the result of Metar arriving from Simconnect with wrong data or not arriving at all, and Metar is used to read the Dew point, and Dew point is used to estimate possible icing.
When Metar is not received or contains corrupted or missing data, and this has been observed mostly when using 3rd party weather engines, GSX reverts to the "simple" strategy of checking JUST the outside temperature, and since it's not possible to get the Dew point from the sim other than the metar ( there's no Simconnect variable for it ), with the simplified strategy, the slippery conditions are not detected as reliably as when we DO have proper Metar reports, which is the NORMAL case.
So what program do you recommend to get the proper reports loaded? Active sky does not seem to be the answer.
-
So you keep looking for a solution? Because "Can not reproduce" sure does not sound like it.
I asked about settings or add-on used, so I could try to replicate it, but nobody replied.
Not with the way I get my AI Traffic injected.
I don't know which way "your" traffic is injected, but I assure you it works with the most popular product that does traffic injection with Simconnect, that is UT Live. Without a PROPER reproduction case, that doesn't involve installing dozen of incompatible freeware and dead products ( like FlAI ), it's difficult to understand why it might not work with "your" AI, without a proper explanation what you are using.
Im not talking about the lights but about the lighting. The apron is pitch black. And again, I do not own KORD V2 for several reasons so I cannot compare.
I can see lights lighting the apron just fine. Do you mean you would prefer to have some kind of background lighting not related to the actual lamp posts ?
So these guys (http://www.fsdreamteam.com/forum/index.php/topic,23500.0.html) are nobody?
That's a post from March 2020, which was BEFORE we updated the KIAH AFCAD to be fully compatible with P3D V5 so yes, it's normal that somebody using it back then would see that problem. The current AFCAD for KIAH dates April 24th 2020 so yes, other than you NOBODY reported it after we updated the AFCAD.
Those pictures were taken with the default AFCAD, no other airport scenery anywhere near, I am not using any AI program coming with AFCADS.
No, these pictures were taken with you not knowing you had another AFCAD in conflict or with you not using our current AFCAD, the one that has been released in April 2020.
Speaking if KIAH AFCAD, have you tried a GSX pushback from gate C19? Position is "connected" with the wrong taxiway and it takes you through the taxiway lighting
I'll obviously check this but how, exactly, this has anything to do with the transmission towers, which are just not there ?
So blocking of an entire taxiway is FSDTs standard (at least back then)? You can even see the ground equipment on your preview screenshots.
You just made my point: they are not a "bug", they have been made intentionally, which should have been obvious by the fact they even have their shadow burned into the ground texture. So you found something you don't like in a 9-years old scenery, which even then, came with a TRIAL version, is not as if we have anything to hide.
I dont know, I have no chance of trying. But then in the US I need exactly 1 handling company for my airline because groundhandling is usually done inhouse there. In Europe you have only have maybe 2-3 different handling companies on a single airport, a few of them you will see at many airports so with (wild guess) about a dozen individual handling textures you get about 90% of westerneurope covered.
Reducing so much the number of liveries, even compared to the FSX version, would be particularly wrong, considering that with no Render to Texture, and so few operators, users would surely want to customize so no, again, the correct approach is to wait to get a better Render to Texture method, without the dangers of DX12.
So what program do you recommend to get the proper reports loaded? Active sky does not seem to be the answer.
There's no need to get any program to get proper Metar reports. Maybe it wasn't entirely clear but, "metar reports" in this case doesn't mean "metar from real world", I was referring to Metar reports from the sim ITSLEF, since the way Simconnect works, you can ask the sim for a Metar report, regardless how this has been obtained so, even if it's not realtime or real and only coming from manually select weather in the simulator, you can get a "Metar" report from the sim, that is data about weather, using the Metar format.
So, regardless who's providing the weather, the Metar from Simconnect should always work the same: we don't know if a Metar came if you selected the weather manually using the sim own interface, or if you used a 3rd party weather generator, for us it's just "the Metar from the sim" and, we observed that, in some cases, if using 3rd party weather generators, the Metar arrives either corrupted, or doesn't arrive in time when GSX asks for it, which doesn't usually happen if the weather is created internally.
That's why we have two strategies to detect icing: the "realistic" one, which uses the Metar from the sim, and the "simple" one, which checks only the ambient temperature variable ( so it doesn't need the Metar ), and the simple one is used as a fallback when there's a problem with the Metar data.
Before we implemented this approach, relying on Metar only, users were convinced GSX had a "bug" detecting icing, because it suggested a de-icer even when outside was hot. This because it got a wrong/missing/late/corrupted Metar from the sim, so after we added the fallback strategy, you will never see GSX suggesting deice in hot weather, since the outside temp variable always work even with no Metar, but in this case we cannot decide based on the humidity factor, so you'll see GSX suggesting deice in any case where there's low temperature.
-
I asked about settings or add-on used, so I could try to replicate it, but nobody replied.
Addons: ORBX Global Base, ORBX Northern America, ORBX Northern California (NOT SoCal!), ORBX KBUR, LVFR SNA
Settings: LOD Med, Tes Hi, Mesh 5m, Tex res 30cm, high res textures, scenery complex dense, autogen distance high, vegetation very dense, buildings dense, dyn 3d autogen off, EA on, road vehicles 75%.
I don't know which way "your" traffic is injected, but I assure you it works with the most popular product that does traffic injection with Simconnect, that is UT Live. Without a PROPER reproduction case, that doesn't involve installing dozen of incompatible freeware and dead products ( like FlAI ), it's difficult to understand why it might not work with "your" AI, without a proper explanation what you are using.
FLAi was not dead back in august (http://www.fsdreamteam.com/forum/index.php/topic,24086.msg160114.html#msg160114)...
I can see lights lighting the apron just fine. Do you mean you would prefer to have some kind of background lighting not related to the actual lamp posts ?
I would prefere lighting where the glow extends more than 2 meters from its source. But what do I know, maybe Charlotte Airport directs their lighting pointing to the ground only.
That's a post from March 2020, which was BEFORE we updated the KIAH AFCAD to be fully compatible with P3D V5 so yes, it's normal that somebody using it back then would see that problem. The current AFCAD for KIAH dates April 24th 2020 so yes, other than you NOBODY reported it after we updated the AFCAD.
The post never got any mention of the fix, how should I know it has been fixed?
No, these pictures were taken with you not knowing you had another AFCAD in conflict or with you not using our current AFCAD, the one that has been released in April 2020.
Ok this is getting ridiculus, I deleted my whole KIAH scenery folder and let the liveupdater redownload it again, the towers are still showing.
I'll obviously check this but how, exactly, this has anything to do with the transmission towers, which are just not there ?
Ok, wont let you know about any more bugs I find in your products. (Wait, your products dont have bugs, its all intentional)
You just made my point: they are not a "bug", they have been made intentionally, which should have been obvious by the fact they even have their shadow burned into the ground texture. So you found something you don't like in a 9-years old scenery, which even then, came with a TRIAL version, is not as if we have anything to hide.
Unfortunatly I dont have the time to restart the Sim hundreds of times to check out every corner in the trial version before I buy a product that may have flaws and blocked off taxiways.
But if your answer on this topic is, that you purposly place equipment on taxiways, I should refrain from purchasing future products.
Before we implemented this approach, relying on Metar only, users were convinced GSX had a "bug" detecting icing, because it suggested a de-icer even when outside was hot. This because it got a wrong/missing/late/corrupted Metar from the sim, so after we added the fallback strategy, you will never see GSX suggesting deice in hot weather, since the outside temp variable always work even with no Metar, but in this case we cannot decide based on the humidity factor, so you'll see GSX suggesting deice in any case where there's low temperature.
Seems like my best bet is to just ignore the suggestion.
-
Addons: ORBX Global Base, ORBX Northern America, ORBX Northern California (NOT SoCal!), ORBX KBUR, LVFR SNA
Settings: LOD Med, Tes Hi, Mesh 5m, Tex res 30cm, high res textures, scenery complex dense, autogen distance high, vegetation very dense, buildings dense, dyn 3d autogen off, EA on, road vehicles 75%.
I'll try with your same settings now.
FLAi was not dead back in august (http://www.fsdreamteam.com/forum/index.php/topic,24086.msg160114.html#msg160114)
The reason why we tested only with UT Live is PRECISELY because we know those freeware project usually die, like WoAI, etc.
I would prefere lighting where the glow extends more than 2 meters from its source. But what do I know, maybe Charlotte Airport directs their lighting pointing to the ground only.
You don't seem to have a clear idea of scale, since those are more like 10-15 meters, not 2 but, whatever, we'll look if we can improve that.
The post never got any mention of the fix, how should I know it has been fixed?
And how this makes any difference ? You said you have that problem NOW, and since this doesn't happen with our current AFCAD, the only possible explanation is either you haven't updated it, or you modified it, or you have a conflict.
Ok this is getting ridiculus, I deleted my whole KIAH scenery folder and let the liveupdater redownload it again, the towers are still showing
And how, exactly, reinstalling KIAH would fix it, if the conflict caused by ANOTHER AFCAD ?
Ok, wont let you know about any more bugs I find in your products. (Wait, your products dont have bugs, its all intentional)
Right now, there isn't a single thing in your report that is a bug.
Unfortunatly I dont have the time to restart the Sim hundreds of times to check out every corner in the trial version before I buy a product that may have flaws and blocked off taxiways. But if your answer on this topic is, that you purposly place equipment on taxiways, I should refrain from purchasing future products.
You seem to intentionally ignore the fact we are discussing a scenery MADE in 2012. How, this, exactly, has any relevance to "future products" ?
Seems like my best bet is to just ignore the suggestion.
Which was EXACTLY as it was before, when GSX didn't use the dual strategy, and always suggested deicing, even when metar was not reliable. But users were annoyed by the deicing suggestion ( and rightly so ) and since many of them asked for a change, we made it, pity it's not the change *you* would see as the "best bet".
-
The reason why we tested only with UT Live is PRECISELY because we know those freeware project usually die, like WoAI, etc.
FLAi was just a compilation of some really good freeware models and repaints, all still available, AIG is basically the same but including the flightplans and most likely the most commen AI traffic in the P3D orbit at the moment.
And how this makes any difference ? You said you have that problem NOW, and since this doesn't happen with our current AFCAD, the only possible explanation is either you haven't updated it, or you modified it, or you have a conflict.
And how, exactly, reinstalling KIAH would fix it, if the conflict caused by ANOTHER AFCAD ?
These accusations are getting ridiculus, I now disabled EVERY SINGLE non-FSDT product and the towers are still popping up so how can anything else interfere with your exclusion??
You seem to intentionally ignore the fact we are discussing a scenery MADE in 2012. How, this, exactly, has any relevance to "future products" ?
My purchase was less then 2 months ago, pardon me for not buying it before. It is not my fault anybody else ignored the fact that your scenery is just wrong. Eqipment parked on a taxiway is one of the biggest no-gos on the ramp. It is relevant for me to see how supportive a company is and how the quality in general is in order for me to keep my business with them. Basic economy.
Which was EXACTLY as it was before, when GSX didn't use the dual strategy, and always suggested deicing, even when metar was not reliable. But users were annoyed by the deicing suggestion ( and rightly so ) and since many of them asked for a change, we made it, pity it's not the change *you* would see as the "best bet".
And again, pardon me to have been out of the hobby of flightsimming for about 8 years and not reading up on all threads
-
FLAi was just a compilation of some really good freeware models and repaints, all still available, AIG is basically the same but including the flightplans and most likely the most commen AI traffic in the P3D orbit at the moment.
Not sure what you are derailing here: you first acknowledged FlAi did, by saying "it wasn't dead in March", now you are moving on AiG.
You said GSX is not compatible with the way YOUR AI traffic is injected. Do you have more details about how YOUR AI traffic is injected ? Since GSX works perfectly fine with traffic injected with UT2, if you cared to add some details about HOW this traffic is generated maybe we could:
- check if the problem is a different method of injection, which is not certain until proven otherwise
- check if the problem might be in the *models* themselves, which is not certain until proven otherwise
- check if the problem might be in the jetway models you are using, , which is not certain until proven otherwise.
My point was, if you will now list an an impossible to recreate situation, like a disappeared AI compilation, or one you heavily customized yourself, that works with yet another different traffic injection program that might require something else too, you would obviously understand why we tested ONLY with default and UT Live, because that's a single click installation, something we can easily reproduce and test.
These accusations are getting ridiculus, I now disabled EVERY SINGLE non-FSDT product and the towers are still popping up so how can anything else interfere with your exclusion??
Something that went into one of the thousands of default scenery folders you cannot easily disable. Something you might have added years ago and forget about it.
And no, you are so wrong about "accusing" you of anything. It's YOU that are accusing KIAH of having a bug that is just not there. Since the bug with V5, which was there until March ( and it was to be expected, since the AFCAD *had* to be updated for V5 ) and has been fixed with our April 2020 update of the AFCAD, I'm telling the only possible options based on YOUR report, which means I BELIEVE YOU it's happening to you.
Since I believe you, the only possible explanations are:
- you don't have the current AFCAD for KIAH
- you have another conflicting scenery.
That's because I believe you have this problem, which doesn't happen anymore with the current AFCAD, which has been online since last year.
My purchase was less then 2 months ago, pardon me for not buying it before. It is not my fault anybody else ignored the fact that your scenery is just wrong. Eqipment parked on a taxiway is one of the biggest no-gos on the ramp. It is relevant for me to see how supportive a company is and how the quality in general is in order for me to keep my business with them. Basic economy.
Which means, if you were so picky about this incredibly minor problem, you should simply not purchase the scenery in the first place, and be grateful we offered you a Trial version ( it that was really important to you, you would have noticed it in Trial ).
That doesn't make any less wrong expecting a 9 years old product made for older simulators to be the same as one made today for the sim you are using now, and also expecting the same level of support or improvement today. Again, we are not hiding anything, the Trial is there for a reason.
And again, pardon me to have been out of the hobby of flightsimming for about 8 years and not reading up on all threads
Then why keep arguing about it, even after my previous explanation in this very thread ?
-
This clearly does not go anywhere, I explained many times how my AI is injected (see the other thread), I explained many times that I have no other AFCAD intentionally installed for KIAH, nor any AI AFCADs somewhere so IF there is a 3rd-party AFCAD, how am I supposed to find it?
You also dont seem to get my point about JFK, do we need to be afraid that in the next products there might be static planes parked on a runway because "back then" they were parked there? If a user is not allowed to point out a flaw in a scenery without getting a snappy answer you could just close this forum.
Thank you for your time but im out.
-
This clearly does not go anywhere, I explained many times how my AI is injected (see the other thread)
Exactly, you made my point: your combination of AI traffic is so convoluted and relying on so many multiple products that, not only it's basically impossible for me to replicate, but it's hardly standard.
, I explained many times that I have no other AFCAD intentionally installed for KIAH, nor any AI AFCADs somewhere so
You can explain it as many times as you like but, fact doesn't change the current version of KIAH doesn't have the problem you are showing, if used with the latest AFCAD and if there are no other sceneries in conflict. So, either you don't have the latest AFCAD, or you have a scenery in conflict.
IF there is a 3rd-party AFCAD, how am I supposed to find it?
For example by running the Simple Airport Scanner.
You also dont seem to get my point about JFK, do we need to be afraid that in the next products there might be static planes parked on a runway because "back then" they were parked there? If a user is not allowed to point out a flaw in a scenery without getting a snappy answer you could just close this forum.
The only one not getting the point here is you, which seem to continue to ignore the fact WE HAVE A TRIAL so, there's no need to be "afraid" of anything, if you want to check how an recent FSDT scenery looks like, you have been given all the means to do so.
-
I don't think PSXseeconTraffic even uses afcads/ade files. Doesn't it use it's own parking algorithm semi based on data in the afcad/ade file? If so, it's probably not going to use jetways.
-
I'm going to chime in and say I too have the floating highway and I do not use ORBX california. I only have OpenLC NA and use v5.1 with the most recent hotfix. I actually had to use scruffyducks software as well to eliminate all of the default scenery but that of course was minor. Settings are pretty modest for my machine which is 10850K 3090 24GB vid card 32 gb ram ssd drives, the whole deal. I was also going to post hoping you can guide in a direction Umberto to help with performance with KLAX but I will get into detail in another thread. Don't want to derail and hijack this thread with other stuff that is irrelevent to the problem at hand here.
-
This thread has been derailed, because DLH7LA converted into a generic rant against FSDT, adding other issues caused by conflicting AFCAD that don't have anything to do with this thread, which is about KLAX.
That floating object at KLAX, which I still cannot reproduce, it's not a problem of a conflicting scenery, since that object IS part of our scenery but, obviously, we surely haven't placed it in the air ( and of course it works with FSX and P3D 1, 2, 3 and 4 up to 4.5. According to your reports, it's only happening with V5, so it's likely a problem caused either by a setting or just an DX12-specific issue but again, unless you could give me some precise reproductions steps, it's impossible for us to even START working on a fix or a workaround, assuming a fix is even possible, and instead the bug will just go away with an update of the sim, just as the supposed bug at KORD V2 ( we also had a floating building there ), which was fixed with an hotfix.
-
In the grand scheme of things a floating highway is the least of my worries vs trying to get my rig to 30fps at klax. If i can get that i really couldnt give a hoot about a floating highway haha.
-
I also have the floating highway on a clean install. I read the forums and know It can’t be reproduced. I just wanted to add my name to the list. I can live with it.
Sent from my iPhone using Tapatalk
-
I also have the floating highway on a clean install. I read the forums and know It can’t be reproduced. I just wanted to add my name to the list. I can live with it.
What do you mean with "clean install" ? Clean install of the simulator ? which means:
- Uninstalling ALL your add-ons first
- Uninstall P3D
- Remove the P3D folder if was still there ( the P3D uninstaller won't do that )
- Remove ALL your settings from %APPDATA%\Lockheed Martin, %PROGRAMDATA%\Lockheed Martin and %LOCALAPPDATA%\Lockheed Martin ( the P3D uninstaller won't do that )
- Remove ALL the folders in Documents\Prepar3d v5 Addons ( the P3D uninstaller won't do that ), to prevent add-ons registered there to restart automatically on the next reinstall.
If you haven't done all of that, is not a clean reinstall.
Or, clean reinstall of the whole OS, which is really clean only if you opted to lose all your program and settings ?
It might have been useful if you could try changing some settings in the sim to see if there's a specific one that might eventually make it disappear, that might give us at least an hint about what could be. I could do that but, since I already said I cannot reproduce it, that kind of help can only come from somebody that can.
Of course, in addition to your precise, exact, settings in the sim, please also indicate which airplane you use.
-
Clean install for me is a brand new PC build with latest Windows 10 install and just purchased P3Dv5.1 on a brand new SSD. I tried the QW787 and the PMDG 737 with same results. I will try different settings and see what effect it has.
-
Clean install for me is a brand new PC build
But since you haven't said that, I couldn't possibly guess it without asking first.
I tried the QW787 and the PMDG 737 with same results
So you made a clean install of Windows, but your simulator already includes some add-ons, so that's not a "clean" install, not of the simulator anyway.
Which other add-ons are you using in P3D ? OrbX perhaps ? According to all reports, the only thing that seems constant is that most that have that issue use something from OrbX.
-
I was having the issue as well.
I tried this below, and it seems to have solved the issue for me.
You might start with resetting your shaders, by removing this folder:
%LOCALAPPDATA%\Lockheed Martin\Prepar3d v5\Shaders
Thanks Umberto
-
I was having the issue as well.
I tried this below, and it seems to have solved the issue for me.
I was fairly sure it wasn't a scenery problem, but an issue with the sim installation, at least in your case but, it surely seem to indicate there's nothing wrong with the scenery itself.
-
So has anyone *actually* found a solution to this bug? Clearing shaders has nothing to do with this.
-
So has anyone *actually* found a solution to this bug? Clearing shaders has nothing to do with this.
The previous user did find a solution that worked for him so, at least in HIS case clearing the shaders HAD a lot to do with this problem, clearly proving the scenery didn't had anything wrong.
If it's not working for you, it's likely something ELSE in your simulator install or configuration that is not right, most likely a tweak or a setting, either in the sim itself, but possibly a tweak in drivers settings too.
-
So has anyone *actually* found a solution to this bug? Clearing shaders has nothing to do with this.
The previous user did find a solution that worked for him so, at least in HIS case clearing the shaders HAD a lot to do with this problem, clearly proving the scenery didn't had anything wrong.
If it's not working for you, it's likely something ELSE in your simulator install or configuration that is not right, most likely a tweak or a setting, either in the sim itself, but possibly a tweak in drivers settings too.
Can you please post a file that removes the highway? I'm done spending time on this.