FSDreamTeam forum
Products Support => Chicago O'Hare V2 for P3D4 => Topic started by: B777ER on August 27, 2019, 12:15:39 pm
-
Why was the no night lighting topic locked? That's very strange as their was no civil discourse in it? Topics here are rarely locked. Multiple users were reporting the same issue yet it's locked without any resolve. Or is the blame going to be cast on end users using shader programs and refuse to believe it could be an issue with your software? WIn my case I run scenery from FT (KLAS) and LatinVFR (KMIA) which are all PBR without any issues. Your KORD night works just fine if starting out by loading the airport from the scenario screen but doesn't when flying to it.
-
I was going to test thisd today.
Does it have to be a full flight or as a test could it be just a nighttime takeoff from KORD and do a 180 and land?
-
As a matter of fact, I'm sorry that this post has been closed, because I've started it and very kindly I have submitted my problem enclosing some screenshots as well hoping to find a solution to this issue....
I woul like to thank Stiarol to having suggested a smart way to get through.
alberto
-
So I just looked at the original thread which got locked. I would just like to chime in and say that I'm having the same issue that the OP is experiencing.
-
I wonder if restarting Couatl on the approach would help?
Problem only seems to occur on incoming flights. Wonder if it could have anything to go with FT Midway? I have pretty much all of the FSDT sceneries , as well as all the new PBR sceneries and have never had this problem, on ORD v2
-
As a matter of fact, I'm sorry that this post has been closed, because I've started it and very kindly I have submitted my problem enclosing some screenshots as well hoping to find a solution to this issue....
I woul like to thank Stiarol to having suggested a smart way to get through.
alberto
What did he suggest? what does he mean by "press ok and let it rebuild"? That post made zero sense to me. Was he talking about deleting the shaders? allowing the scenery cache to rebuild? I tried both and it made no difference. Were you able to understand his post and fix the problem on your end? Could you elaborate (make clear) on your statement "suggested a smart way to get through"?
I don't understand why or how that topic was closed, I can only guess that Umberto confirmed the issue and is working on sorting the problem out at least I hope that is the case. Until then I consider this daytime scenery only.
-
before landing, as soon as you can see the airport, you can open menu of p3d.. than world..than scenery and than only press ok......
and like a miracle the scenery reloads perfectly and you can do a good night landing in a good airport without issues...
-
before landing, as soon as you can see the airport, you can open menu of p3d.. than world..than scenery and than only press ok......
and like a miracle the scenery reloads perfectly and you can do a good night landing in a good airport without issues...
If one has to do that to get the scenery to work, then "without issues" is not true. I for one will not be doing that. I.see Umberto has been in the forum answering posts but has chosen to ignore this one. If he thinks this problem is going to go away by ignoring us then that's not going to happen.
-
Yesterday I was away the whole afternoon, and since Alessandro ( KORD's author) is on a very short vacation until Friday, he likely locked the thread so people won't assume "I wasn't responding" for the whole day.
Anyway, back on the topic at hand it seems this problem is in fact another simulator bug, and it has been known since 2018, see this post from Aerosoft:
https://forum.aerosoft.com/index.php?/topic/132680-no-dynamic-lighting-at-destination/
We never got to encounter it before, simply because ( AGAIN ), when objects the DL effect are attached to are created as Simobjects, the problem doesn't happen, and since we USED to make most of our scenery using dynamically created Simobjects, we weren't affected by this in KCLT or KSDF. And, we couldn't noticed during KORD developement, because we started by doing everything as Simobjects, like we usually did, and converted most of it back to .BGL in the last days, because we wanted to be the scenery to load as smooth as possible and not use Simobjects if wasn't really necessary.
So, again, just like the "floating object" bug, which wouldn't have happened if we relied on Simobjects created by Couatl, we were affected by another bug of the simulator because we decided to be as standard as possible with KORD V2.
Fortunately, there IS a workaround for this, without having to be forced to convert even the general DL into Simobjects, which of course is already up on Live Update now, together with the other problem reported of bumps at the end of the the northern runway.
-
I've run Live Update each day so I should have the changes - I'm still experiencing the DL issue on arrival. Spawning at the airport DL works fine.
-
I've run Live Update each day so I should have the changes - I'm still experiencing the DL issue on arrival. Spawning at the airport DL works fine.
Sorry, but nobody else has ever reported this after the fix. Try to run the current KORD full installer instead of the Live Update.
-
I will give it a try.
I can report that last night I did a flight into KORD, and all the area DL around the terminal buildings were off. As I pulled up to the gate, the DL lighting at the terminal I parked at suddenly illuminated, yet all the other terminals were still dark.
PC hardware, I'm using an 8700k / Strix GTX 1080ti. I'm monitoring the Vram usage and notice that taxiing around KORD, Vram can go as high as 10g, and in some places drop to 7g. On arrival, vram doesn't go higher than 6g, so it's not a matter of running out of resources.
-
After uninstalling and reinstalling, I'm having the same issue. The airport is pretty much dark on arrival and after landing. There's only a slight glow from the buildings. It's only after I pull up to a gate, that the DL on that terminal illuminates. The remaining buildings are still dark.
Spawning at the airport at night has no problems. If I clear the scenery cache while in the sim, the DL then works.
-
I'm sorry but, I can only repeat and confirm that all DL works even when starting on an airport and landing at KORD and, after we issue the fix, nobody ever reported it again.
Note that, the overall DL, are handled by the simulator ( the ones that "works" for you are handled by the Couatl engine, that's why they always work ) and, they might not appear if the simulator has decided you have too many DL active at any given time, there's an overall limit which I think it's about 200, but I'm not sure so, possibly, if another add-ons in the area have added their own DL and the overall limit has been reached, the extra ones won't appear.
-
Thanks - that may make sense. There is another add-on that could be utilizing too much DL. I'm going to change some settings and try again.
-
I thought the issue may have been the night lighting add on was utilizing the DL overhead, but that doesn't appear to be the case. With the night lighting disabled, I'm still not getting any DL on approach or after landing, until I pull right up to the gate, and then only the building I'm parked at will illuminate.
If I refresh the scenery cache, then all the DL works. Not sure what else to do.
-
I thought the issue may have been the night lighting add on was utilizing the DL overhead, but that doesn't appear to be the case.
It likely is, otherwise other users would have reported it by now, if it really were a problem of the scenery. Yes, it was reported before the fix, we fixed it, and nobody else except you has reported it again, after the fix.
With the night lighting disabled, I'm still not getting any DL on approach or after landing, until I pull right up to the gate, and then only the building I'm parked at will illuminate.
If I refresh the scenery cache, then all the DL works. Not sure what else to do.
Your description of the problem indicates that:
- the DL which are made as a standard .BGL, so they are handled entirely by the simulator without any control on our part, other than just placing the lights, are not working.
- the DL which are created by our Couatl engine (so they could appear/disappear only when you are close to the terminal) ARE working.
The problem is, making also the other lights handled by the Couatl engine, will likely fix this issue but, the more objects we create dynamically, the more the scenery will cause pauses when loading, so we wanted to use them only when absolutely necessary, and stick with the .BGL format for everything that is not supposed to go in/out based on some condition, which is the case of the background lights.
So, before taking some extra action, I would wanted to get at least another user report still having the same issue after the fix.
-
Was hoping someone else would add to this post with similar results.
I've turned my sim graphics settings down and yet I still don't get any DL from the canopy lights until I'm parked at the gate (and then only at that building). Arriving at night, the buildings are all dark.
What's odd is this is the only airport this happens to. All my other FSDT airports looks beautiful at night, no problems at all.
-
I have noticed while flying into KORD V2 that most times the dynamic lighting wont load. I am up to date on fsdt and prepar3d 4.5 hotfix 2 content, client and scenery. Latest graphics drivers. I can shutdown the sim and load into KORD and then it will be fine any ideas? It should work as im flying into the airport correct? and even when im close to gates still nothing TIA:)
-
You know I’m getting the exact same thing. What’s going on with this scenery? You know I’ve been very patient about all these bugs but it’s starting to get annoying. From flashing triangles to this now? Come on this is ridiculous.
-
You know I’m getting the exact same thing. What’s going on with this scenery? You know I’ve been very patient about all these bugs but it’s starting to get annoying. From flashing triangles to this now? Come on this is ridiculous.
I’m not the only one with the dynamic lighting issue. Good to know I have heard it from other developers too and they have been able to fix it so hoping that’s the issue :)
-
I've reported this issue and was told there were no other users experiencing the problem, and they weren't going to investigate until others speak up. Now I'm glad others have, but also look for a fix.
And to restate what my issue is, upon arriving at KORD at night, no DL is visible until I pull right up to the gate and stop, then only the lights at the building will illuminate. I can see the lights from the canopy are on, but they are not projecting DL light onto other objects.
I don't have this issue at any other FSDT airport (or any other devs airport).
Hoping to get this fixed. Thanks
-
And to restate what my issue is, upon arriving at KORD at night, no DL is visible until I pull right up to the gate and stop, then only the lights at the building will illuminate. I can see the lights from the canopy are on, but they are not projecting DL light onto other objects.
This is not a "problem", of course. It's a good scenery FEATURE, which is clearly explained at Page 10 of the KORD V2 manual, when Dynamic Lighting is explained:
We have two sets of Dynamic Lights:
- A “Global” set which is always enabled, that creates a background ambiance, to prevent the airport from being entirely dark in the distance.
- Several “Local” set of lights, placed around the terminals to simulate light pylons, that contribute with an additional lighting to the user airplane or AIs
The Local sets are handled by our software modules, using our special Collision areas, which are logical boundaries that can have their own shapes precisely defined. With this method, the Local light sets are not created until your airplane enters inside this invisible boundary, which matches the shape of each Terminal. This way, DL related to terminals other than the one your airplane is located on, will not show, only a single Local set is ever loaded at any given time. This keeps the total number of DL active under control, to keep fps up.
This way, KORD V2 can enjoy total and full DL ( *all* lights are dynamic and use PBR ), without the big associated cost in fps seen in other scenery, which either have very low fps with DL on, or had to reduce the number of DL a lot, and fall back to legacy baked illumination, which of course doesn't look nearly as good as DL, especially with PBR materials.
-
Once again another ridiculous excuse. This is pathetic now. I’m sorry but I have had enough of this crap. The DL works fine if you load into the airport but it doesn’t when we fly in. Now we get excuses about boundaries, local sets and “collision areas”. FIX THE SCENERY. IT IS BROKEN AND HAS BEEN SINCE DAY ONE!!!. I’m seeing it more and more now with you fraudster developers denying reality. Us real summers out here can see it right in front of our face. Oh and by the way, this issure is not “SOLVED”. Far from it. Get to work Umberto.
-
Yes, we USED to have a problem with DL lights not appearing on ARRIVAL on the INITIAL release, but this was FIXED in the August 28th update, only 5 days after the scenery came out:
https://www.fsdreamteam.com/couatl_liveupdate_notes.html
August 28th 2019
Bugfix KORD V2 - Fixed issue with Dynamic Lights not appearing arriving from another airport.
THAT problem doesn't happen anymore.
I was explaining something entirely different, which are SOME Dynamic Lights which only appear when you enter IN a parking, and those are supposed to work like that and only show up when getting close.
-
I am having the same issue. If you load into the airport it is fine. When i land at the airport it is terrible. I have done many updates since August 28th and i have the same results. If the problem is solved, How do you fix it?
-
I am having the same issue. If you load into the airport it is fine. When i land at the airport it is terrible. I have done many updates since August 28th and i have the same results.
That's what used to happen before the fix.
If the problem is solved, How do you fix it?
Nothing, we fixed it with the August 28th update. DL lights are working fine when landing now, except the apron lights, which are supposed to work only when getting close.
Have you maybe installed a shader modification ?
-
I am having the same issue. If you load into the airport it is fine. When i land at the airport it is terrible. I have done many updates since August 28th and i have the same results. If the problem is solved, How do you fix it?
I also dont use any shader modifications so that reason is out the window
I have also done the updates and im STILL having the issue.
I really like how you guys have designed the lights that way but when it doesn't work thats a problem Is there a way to disable the 2 sets of dynamic lights and just make them on all the time?
We have two sets of Dynamic Lights:
- A “Global” set which is always enabled, that creates a background ambiance, to prevent the airport from being entirely dark in the distance.
- Several “Local” set of lights, placed around the terminals to simulate light pylons, that contribute with an additional lighting to the user airplane or AIs
The Local sets are handled by our software modules, using our special Collision areas, which are logical boundaries that can have their own shapes precisely defined. With this method, the Local light sets are not created until your airplane enters inside this invisible boundary, which matches the shape of each Terminal. This way, DL related to terminals other than the one your airplane is located on, will not show, only a single Local set is ever loaded at any given time. This keeps the total number of DL active under control, to keep fps up.
As he says here your plane enters inside a boundaries (by the terminals) it should activate the lights by the airplane. It should be almost instant right?
Am i understanding this correctly?
And I don’t think this has been stated either could a reinstall of the scenery maybe fix the issue?!
-
I have created a video to show you the issue i am having
Flying from KMKE -> KORD not close to KORD to have it render other lights etc before getting to kord.
Time stamps are as follows
BOTH TIMES @ Gate F21
Hopefully this can help you find the issue with the dynamic lighting at KORD
for landing 1:56
Gate 6:00
ISSUE 7:00
Reload but FSDT crash 7:30
Reload and what it should look like 8:20
ones in bold are ones you need to see look at the GROUND and AIRCRAFT
-
Yes, General Aviation, this is the same issue I am having as well. Thanks for the great post.
-
General Aviation, I couldn’t have put it better. Thanks for posting the video of the EXACT same issue I’m having. The DL is great at the new KORD but we want to see it after we land as well.
-
Your video shows you surely must have some kind of 3rd party lights enhancement, since I can see *hundreds* of lights on approach on roads, cities, which are not normally present.
Each of these light is an Effect, and there's a limit on the total number of effect the simulator can show at any given time. I'm not fully sure how many effects in total, but by default no more than 250 Dynamic Lights can be created. In fact, the Prepar3d.cfg file has two settings to control this limit:
MAX_POINT_LIGHTS=250
MAX_SPOT_LIGHTS=250
You might TRY to change these and see if it makes any difference.
About the maximum number of Effects ( the lights on roads are Effects lights not Dynamic Lights) but wouldn't expect them to be "infinite" either and, which one are turned off/on when you go over the limit, is of course entirely outside our control, and it's even possible that too many regular Effects at once MIGHT affect the Dynamic Lights, which in fact *are* Effects, just with some extra parameters.
Also, you image is very dark, have you HDR turned off perhaps ?
-
ok so if that were the case, the DL should not work when we load in as well correct? those "other lights" are still there even when we load directly into the airport.
-
Just landed at KORD - lights are off on all the terminals.
I ran the FSDT update manager before starting the flight - so what's the issue?
-
Just made a 16 hr from OMDB into a cold and dark KORD. ??? >:( :-\
-
So it seems this is intended behavior in how DL appears on arrival. I'm glad at least there's nothing wrong with the installation, or missing files.
There's certainly a difference in DL light cast when a flight arrives vs when it spawns at a gate. Other than the taxi/runway lights, the entire airport appears dark when arriving at night (and the green building glow) but I get why it's setup this way, and most likely a limitation to how P3d handles DL as a whole.
-
Your video shows you surely must have some kind of 3rd party lights enhancement, since I can see *hundreds* of lights on approach on roads, cities, which are not normally present.
Each of these light is an Effect, and there's a limit on the total number of effect the simulator can show at any given time. I'm not fully sure how many effects in total, but by default no more than 250 Dynamic Lights can be created. In fact, the Prepar3d.cfg file has two settings to control this limit:
MAX_POINT_LIGHTS=250
MAX_SPOT_LIGHTS=250
........
Also, you image is very dark, have you HDR turned off perhaps ?
Yes I did use black marble night lighting and I flew into kord again without nightl ighting and same result . No I do not use HDR but I have enabled it to do a little bit of testing and with it on I’m still seeing this issue. Also I would like to point that when i uninstalled black marble I immediately got the black triangles issue witch I have only seen a few times. I did not get triangles with black marble installed
Any airport that you make should be compatible out of the box with the most common Addons
Editing the config file: yes I do know that prepar3d can only have so many dynamic lights at one time and I changed it to 500 and that made performance really bad and still did not fix the issue. but why aren’t KORD’s higher in priority while at the airport. I understand if they don’t work while flying over but once your on the ground they should be the top priority am I wrong?
And again I don’t know if it’s just me but I only have this issue at KORD V2 that’s it just very confused
Also what settings would you recommend to run the scenery in the graphics control panel in the sim. I use a 8700k,1080ti and 32gb of ram.
I think I can almost speak for everyone but what I look for in a scenery is simplicity. I don’t want to have to edit config files and stuff to make it work. It should just be a install and fly. (I understand if there are scenery settings that’s not what I’m getting at)
Thank you for keeping on top of this issue
EDIT
Just flew into KORD with the tweaks in prepar3d.cfg and i set it from 250 -> 500 no difference ^as i stated above and i uninstalled black marble and i still have as many lights as i did FYI.
-
ok so if that were the case, the DL should not work when we load in as well correct? those "other lights" are still there even when we load directly into the airport.
We don't have any control over the simulator own strategy to decide which and when DL are removed when the limit is reached.
-
Yes I did use black marble night lighting and I flew into kord again without nightl ighting and same result . No I do not use HDR but I have enabled it to do a little bit of testing and with it on I’m still seeing this issue. Also I would like to point that when i uninstalled black marble I immediately got the black triangles issue witch I have only seen a few times. I did not get triangles with black marble installed
If installing and uninstalling that addon DID make a difference ( even if it appear to "improve" it ), it clearly proves KORD is not the problem, which of course has been proven already multiple times since:
- Only some users reported it, not the many thousands already bought KORD V2
AND
- Several users confirmed they have black triangles ELSEWHERE TOO.
So, it's quite clear the black triangles must be a problem of a specific combination of driver settings, simulator settings and installed add-ons that, for some reason, disappear with an add-on that doesn't have anything to do with KORD, but it's possible it has changed some setting that apparently "fixed" it. On YOUR system, of course, since the problem doesn't normally happen.
Any airport that you make should be compatible out of the box with the most common Addons
Nope. An airport should be compatible with the bare bone simulator installer and be made to SDK specs, and that's what KORD V2 obviously is, a purely 100% P3D4 NATIVE scenery.
It's clearly not possible for anybody to test a scenery with all the hundreds of add-ons, that's why we sell the scenery as Try-before-buy. Do ALL the other add-ons you have, one of which is surely the main cause of this problem, offer you this option ?
but why aren’t KORD’s higher in priority while at the airport. I understand if they don’t work while flying over but once your on the ground they should be the top priority am I wrong?
DL light priority is entirely outside our control, and I doubt is related in any way to the Scenery Library priority.
I think I can almost speak for everyone but what I look for in a scenery is simplicity. I don’t want to have to edit config files and stuff to make it work. It should just be a install and fly. (I understand if there are scenery settings that’s not what I’m getting at)
That's exactly how KORD works out of the box. But if you install lots of other add-ons, you are causing the complexity increase. We surely don't require more than 250 lights at KORD. In fact, the manual clearly explains how we managed to keep them to a MUCH lower count than any other add-on out there.
-
yet I still don't get any DL from the canopy lights until I'm parked at the gate (and then only at that building). Arriving at night, the buildings are all dark.
Have you read the manual about DL, and all my previous posts ?
Those close-up light are SUPPOSED to behave like that and, incidentally, those are the only ones which are handled by our software, the ones you are missing are the ones we DO NOT manage, but are supposed to always work, since they are in a plain .BGL and handled by the simulator itself.
So, if you are really missing only the main global lights, and the only lights you see are those that appear when you are close to a gate, it means the only thing working correctly here is the FSDT software that handles dynamic lights, while the system handled by the simulator is not working for some reason, most likely caused by too many effects, due to other installed add-ons.
Have you installed 3rd party add-ons that "enhance" lights ?
-
Yes I did use black marble night lighting and I flew into kord again without nightl ighting and same result . No I do not use HDR but I have enabled it to do a little bit of testing and with it on I’m still seeing this issue. Also I would like to point that when i uninstalled black marble I immediately got the black triangles issue witch I have only seen a few times. I did not get triangles with black marble installed
If installing and uninstalling that addon DID make a difference ( even if it appear to "improve" it ), it clearly proves KORD is not the problem, which of course has been proven already multiple times since:
- Only some users reported it, not the many thousands already bought KORD V2
Ok so if some are reporting it you should still look into it because almost no one uses the sim stock I would never consider making a add on that was not compatible with the most used common addons
So, it's quite clear the black triangles must be a problem of a specific combination of driver settings, simulator settings and installed add-ons that, for some reason, disappear with an add-on that doesn't have anything to do with KORD, but it's possible it has changed some setting that apparently "fixed" it. On YOUR system, of course, since the problem doesn't normally happen.
Yes that is very true and I agree to that but I have has this issue from a FULL REINSTALL on STOCK A settings in a stock sim.
Any airport that you make should be compatible out of the box with the most common Addons
Nope. An airport should be compatible with the bare bone simulator installer and be made to SDK specs, and that's what KORD V2 obviously is, a purely 100% P3D4 NATIVE scenery.
again very very few people if any use the sim without some kind of add on of any kind if I knew it wasn’t compatible due other addons using resources in the sim that would cause features not to work properly I would NOT have bought it!
It's clearly not possible for anybody to test a scenery with all the hundreds of add-ons, that's why we sell the scenery as Try-before-buy. Do ALL the other add-ons you have, one of which is surely the main cause of this problem, offer you this option ?
yes I do know that and it’s a great thing but when you get about 15 miles from the airport on app by the time your on the ground the trial ends and it’s pointless
but why aren’t KORD’s higher in priority while at the airport. I understand if they don’t work while flying over but once your on the ground they should be the top priority am I wrong?
DL light priority is entirely outside our control, and I doubt is related in any way to the Scenery Library priority.
Ok now thats good to know
I think I can almost speak for everyone but what I look for in a scenery is simplicity. I don’t want to have to edit config files and stuff to make it work. It should just be a install and fly. (I understand if there are scenery settings that’s not what I’m getting at)
That's exactly how KORD works out of the box. But if you install lots of other add-ons, you are causing the complexity increase. We surely don't require more than 250 lights at KORD. In fact, the manual clearly explains how we managed to keep them to a MUCH lower count than any other add-on out there.
Ok then why do I only has this issue at KORD V2
I have a few questions to ask if you say it works
Do a flight from the Gary/Chicago airport and just fly into KORD at night by the time selection and selecting NIGHT AIN THE DROP DOWN and taxi to a gate and WAIT post the full video because to this day you have not shown us pictures or video saying that YOU don’t see this issue.
Post your simulator settings in the video too
Secondly do you ever really “fly” load up in a airport with payware airplanes and fly into a airport yours or not yours. It does not seem like you understand how these little details are important to real simmers.
These would be appreciated thank you
-
All the buildings at KORD are dark - can't see them. Only runway and taxi lights work.
-
So what do I need to do to fix this?
-
So what do I need to do to fix this?
He hasent said hes gonna fix it. The only way you can "Fix it" Is by using the DEFAULT simulator with nothing added into it. Its really disappointing
-
So what do I need to do to fix this?
He hasent said hes gonna fix it. The only way you can "Fix it" Is by using the DEFAULT simulator with nothing added into it. Its really disappointing
Hey virtuali - That's OK if you don't want to. Can I go back to an older version that worked then bro? :) KIAH works fine as the others.
-
So what do I need to do to fix this?
He hasent said hes gonna fix it. The only way you can "Fix it" Is by using the DEFAULT simulator with nothing added into it. Its really disappointing
Hey virtuali - That's OK if you don't want to. Can I go back to an older version that worked then bro? :) KIAH works fine as the others.
If there is a way to go back in a version LET ME KNOW! As far as i know you cannot and yes i agree KIAH does work along with others just KORD v2 has this issue
-
All the buildings at KORD are dark - can't see them. Only runway and taxi lights work.
Im having the same issue and I know of many others who are also having the issue
-
All the buildings at KORD are dark - can't see them. Only runway and taxi lights work.
Im having the same issue and I know of many others who are also having the issue
I have Chicago X installed too (Just the city). However, KORD is above Chicago City X - but it worked in the over version.
-
Ok so if there are to mamy effects, than why does it work properly if you spawn in at the airport? The other addons are still present.
-
Ok so if there are to mamy effects, than why does it work properly if you spawn in at the airport? The other addons are still present.
As I've said in another post, we don't have any control over the simulator own strategy of which and when remove the extra effects.
-
Do a flight from the Gary/Chicago airport and just fly into KORD at night by the time selection and selecting NIGHT AIN THE DROP DOWN and taxi to a gate and WAIT post the full video because to this day you have not shown us pictures or video saying that YOU don’t see this issue.
Post your simulator settings in the video too
There you have it. Gary to KORD at night. PMDG NGXu + DD Chicago City + Airports ( without KORD, of course ). My settings are attached.
-
yeah im at a loss for words. I don't know what to say anymore. very disappointing.
-
Wait! All is not lost!!! I am not sure which actually fixed the issue but here is what I did:
-deleted the Prepar3D.cfg (C:\Users\<XXX>\AppData\Lockheed Martin
-Restarted P3D to generate a new .cfg file
-tweaked as necessary (Using CptVince's settings because we have similar systems but made my own adjustments to the NON-GRAPHIC sections)
*including adding this to the newly created .cfg: OPAQUE_SHADOW_TEXTURE_SIZE=4096
*he nor I touched Dynamic Reflections (set to off)
Fired up P3D at KORD active runway at 21:00 and I can see the terminal ;D
Hope this helps
-
Wait! All is not lost!!! I am not sure which actually fixed the issue but here is what I did:
-deleted the Prepar3D.cfg (C:\Users\<XXX>\AppData\Lockheed Martin
-Restarted P3D to generate a new .cfg file
-tweaked as necessary (Using CptVince's settings because we have similar systems but made my own adjustments to the NON-GRAPHIC sections)
*including adding this to the newly created .cfg: OPAQUE_SHADOW_TEXTURE_SIZE=4096
*he nor I touched Dynamic Reflections (set to off)
Fired up P3D at KORD active runway at 21:00 and I can see the terminal ;D
Hope this helps
interesting find. But try flying into the airport. DL has always worked when spawning in at the airport
-
Wait! All is not lost!!! I am not sure which actually fixed the issue but here is what I did:
-deleted the Prepar3D.cfg (C:\Users\<XXX>\AppData\Lockheed Martin
-Restarted P3D to generate a new .cfg file
-tweaked as necessary (Using CptVince's settings because we have similar systems but made my own adjustments to the NON-GRAPHIC sections)
*including adding this to the newly created .cfg: OPAQUE_SHADOW_TEXTURE_SIZE=4096
*he nor I touched Dynamic Reflections (set to off)
Fired up P3D at KORD active runway at 21:00 and I can see the terminal ;D
Hope this helps
interesting find. But try flying into the airport. DL has always worked when spawning in at the airport
I was getting dark night time textures both ways. I'll try a KCGX to KORD to validate
-
I used your settings and i had lights! YAY
I put my config back in and it didnt work
Any ideas?
-
Umm same here! Grrrr!
Maybe we are using new drivers and V isn't? I do not know - this is where he has to come in. I will give DD's KORD a try.
I hope whatever new textures V used in KORD v2 isn't applied to all the other FSDT airports until this is sorted out.
-
I used your settings and i had lights! YAY
That it was a settings problem, and NOT a KORD V2 problem, it was quite clear.
I put my config back in and it didnt work
Any ideas?
Difficult to say, without looking at them. Could be some specific setting, or maybe yours were just too high, so the simulator started to reduce things to keep fps up ?
-
It seems that HDR must be on too. Once you turn it off - it's like a military airbase on night time combat readiness drills ;D.
I think ENABLING HDR is mandatory requirement for KORD v2 at night.
Which really makes Chicago X pop, so it's a win win. I use to have it off back when Win10 and HDR didn't play well together.
I think we can consider this "SEMI-SOLVED LOL" :P
That said, I would like KORD a tad more lit up. I have taken some night flights out of there and it's very bright on the tarmac.
-
It seems that HDR must be on too. Once you turn it off - it's like a military airbase on night time combat readiness drills
HDR should always be enabled with PBR.
The main reason for wanting to turn it off, is that at night, some legacy sceneries are too bright, because some night blending mode have changed compared to FSX so, HDR-off is basically there for backward compatibility with older sceneries.
-
It seems that HDR must be on too. Once you turn it off - it's like a military airbase on night time combat readiness drills
HDR should always be enabled with PBR.
The main reason for wanting to turn it off, is that at night, some legacy sceneries are too bright, because some night blending mode have changed compared to FSX so, HDR-off is basically there for backward compatibility with older sceneries.
Interesting - I didn't know that, maybe that should be more clear to those of us that don't speak computer graphics and object rendering LOL ;D