FSDreamTeam forum
Products Support => Zurich scenery for FSX/P3D => Topic started by: Ursli80 on September 21, 2014, 12:10:30 pm
-
Hello Dear Simmer.
Since I can not speak English I must sorry it Translate Translation by
I have re-installed the P3D v2.3 and I've bought from FSDT LSZH and LSGG because AS is not lit at night.
Now I've noticed that flicker the buildings at the airports and the people running back value.
To your help I would be very grateful.
My PC:
Motherboard: Asus Formula V
Graphics card: Nvidia GTX 680 driver 337.88
16GB Ram
2x 250 SSD (1x only for Flusi)
4 core 4.6 GHZ PROZI
About your help I would be very grateful.
Greetings from LSZH
Urs
-
Now I've noticed that flicker the buildings at the airports
Try to turn off some of the shadow casting options in the P3D graphic settings page, it's possible that what is flickering are shadows, because you turned everything on on that page.
and the people running back value.
That's a P3D bug we can't fix on our site. The animation works correctly in FSX.
-
Good Day
Thanks for the tips. Unfortunately, it is not because of the shadow settings.
I can fix the whole thing with reset means Couatl Manager. Now I have the problem that I have no more RWY lighting at night and GSX is no longer available. Do you have a solution?
Many thanks for your efforts.
Best regards
Urs Roth
-
.I can fix the whole thing with reset means Couatl Manager. Now I have the problem that I have no more RWY lighting at night and GSX is no longer available.
I don't fully understand you.
What do you mean with "reset means Couatl Manager" ? There's the Couatl program, and the Addon Manager program, what you did to them and what do you mean with "I can fix the whole thing" ?
-
Excuse me. Unfortunately, I must have the Goggle- Translator work because I can not speak English.
I've been using the program Couatl a reset performed. After that I had no more flare to the buildings. For the RWY lights are no longer present with me since there and GSX I can not even call since there.
I hope that it is now easier to understand.
Excuse me.
Urs Roth
-
I still don't understand what you mean with "reset"
-
Good day.
Excuse me.
I pressed the refresh option there. I had reset in the head.
Therefore Sorry my wrong information.
best regards
Urs Roth
-
Do you have a solution for the people? This running with me backward value instead of forward.
best regards
Urs Roth
-
Do you have a solution for the people? This running with me backward value instead of forward.
As I've said, since they works correctly in FSX, it means the animation is made correctly, and that's just a P3D bug that only LM could fix.
-
Good day
So LM says the problem must in your beds.
Now again the problem of LSZ and LSGG airport have worked during the first installation.
As I clicked by mistake when Coutal-powered products restart Coutal and since then I have at both airports no longer RWY lighting at night.
I have P3D v2.3 Fixed and airports reinstalled. Unfortunately, that did not go well.
What is there for a solution?
best regards
-
I've found something.
If I choose the exterior and go up, I see the lights.
When I go back down to the cockpit or they are gone.
I hope I can add photos.
I ask for a solution.
best regards
Urs Roth
-
Good day
I now have the simulator installed from scratch, as I have unfortunately received no answer from you. Now I have the lights again. Only now the problem is that the lights seem to float over the runway.
Do you have a solution? It is in LSZH and LSGG.
Many thanks for an answer.
best regards
Urs Roth
-
I now have the simulator installed from scratch, as I have unfortunately received no answer from you.
I replied several times, but about the lights issue, I can only say I can't replicate the problem. Nor anybody else has reported it.
Now I have the lights again.
That would indicate the problem was some kind of wrong setting or a problem in the installation of the sim, not a problem of the scenery. Which explain why nobody has reported it.
Only now the problem is that the lights seem to float over the runway.
They are supposed to be raised, otherwise they will flicker and, except for the centerline lights, they are raised from ground even in reality. But in order to prevent flickering, even the centerline are a bit raised from ground.
-
So this is on purpose so that the float?
-
So this is on purpose so that the float?
Yes, if it's not much.
-
Okey. Nur komisch das es bei der Esten Installation normal war.
-
Okey. Nur komisch das es bei der Esten Installation normal war.
Please, use English.
If you are referring to the use of the P3D Migration Tool, it should be kept disabled when using any of our products under P3D, because they DO recognize P3D and they DO *different* things depending if they recognize they are running into P3D or FSX and, since the Migration Tool fools products into believing they are always running under FSX, it would cause all sort of problems with our products, because they are prevented to detect P3D.
This might not be a big problem at Zurich, but it surely cause issue with lots of other more recent products.
-
Dear Support Team
Yesterday I went to the colleagues who also uses P3D v2.3 and FSDT LSZH and LSGG. In this, the lights are mounted normal and not hover over the runway.
Therefore, your statement is not true that this is normal!
I ask you to give me a solution or I want my money back and I uninstall also like the addons in this case again.
best regards
Urs Roth
-
In this, the lights are mounted normal and not hover over the runway.
Therefore, your statement is not true that this is normal!
My statement is obviously true because, as I've said, they are raised A BIT, to prevent flickering.
You haven't said how much they were raised in YOUR installation so, I couldn't say if you were seeing was the normal, very small, rising over ground that the light ARE supposed to have, or something much larger, which would indicate some kind of a problem.
I ask you to give me a solution or I want my money back and I uninstall also like the addons in this case again.
Since all our products are available in Trial, you cannot obviously ask for a refund.
And even more, considering YOU said yourself the same scenery works correctly on another system, under P3D too. This clearly indicates the scenery doesn't have the slightest problem (which should be quite obvious, since it has been released many years ago, and nobody else reported this problem), that it works in P3D, and your problem is caused by a specific of your installation, not by the scenery, that's why you can't ask for a refund.
You might try resetting all your settings, by removing the following folders:
%PROGRAMDATA%\Lockheed Martin\Prepar3D v2
%LOCALAPPDATA%\Lockheed Martin\Prepar3D v2
%APPDATA%\Lockheed Martin\Prepar3D v2
%USERPROFILE%\Documents\Prepar3D v2 Files
In fact, this is what LM suggest to ALWAYS do after installing a new P3D version, and if you don't do that, you'll see all kind of graphic anomalies.
-
So I need all the values in this folder deletion?
% ProgramFiles% \ Lockheed Martin \ Prepar3D v2
LOCALAPPDATA%% \ Lockheed Martin \ Prepar3D v2
% APPDATA% \ Lockheed Martin \ Prepar3D v2
% USERPROFILE% \ Documents \ Prepar3D v2 Files
Or how I have to understand with the resetting?
I have bought your products that do not run as a trial for me.
Why was in another post said that this was normal, that the lights on the runway are?
regards
Urs Roth
-
So I need all the values in this folder deletion? Or how I have to understand with the resetting?
You need to remove all those folders, this is what LM says you must do, when updating P3D to a new version.
I have bought your products that do not run as a trial for me.
Are you saying you bought the products, even if the Trial didn't work ? Why ? The whole point of having a Trial is that you can check they WORK (and they surely do) BEFORE purchasing them!
Why was in another post said that this was normal, that the lights on the runway are?
You don't seem to understand. Re-read my last message, carefully.
I've said that A BIT of raising is normal, and it's barely noticeable, but I can't possibly know how "noticeable" means for you, since it wasn't clear at all, from your previous messages, HOW MUCH of a raising you saw.
Now that you say you haven't seen any rising on another system, it's finally clear that you don't notice the small raising that IS definitely there and it IS normal, so you must have seen something way larger, but that's not how the scenery is made, or like anyone else is seeing, so the only possible explanation left, is that you have a problem with your P3D settings, that might be fixed by resetting the preferences, which is what you should do anyway, according to LM instructions when applying an update.
-
I've bought your products since I fly to the Council's attention by a colleague new with P3D.
I have already told you that this worked correctly even at the beginning.
I have this problem since I've only been on the Restart Button Couatl the Couatl-powered product instead of the key mappings.
This is what I always said to the reset.
So once again:
Product tested = works Works then bought =. Then accidentally Restart Couatl come RWY lights = no more. Then to see all newly installed = resist lights aberr too high.
I have you now made images.
best regards
Urs Roth
-
Your screenshots are not very clear. They shows a very *minor* rising which, as I've said, it's entirely NORMAL for runway lights.
Also, they don't have any relationship with the Couatl program, since they are generated by the scenery AFCAD, using the default light system handled by the sim so, it's just not possible they could have any relationship with the Couatl program.
Of course, just to be sure, I tried installing Zurich on the recently released P3D 2.4, freshly installed, and no, I can't see any problems the lights, and nothing happens when selecting the "Restart Couatl" option.
So, I can only confirm the problem doesn't have anything to do with the scenery, and it must be something related to your settings.
I already indicated what you have to do reset the P3D settings, be sure you do that, before updating to 2.4. As an alternative, UNINSTALL P3D and reinstall the 2.4 version using the 2.4 full installer.
-
For what it's worth, I am also having this issue. Tried clearing out my shaders and this had no effect on the flickering buildings.
-
For what it's worth, I am also having this issue. Tried clearing out my shaders and this had no effect on the flickering buildings.
If you are referring JUST to the flickering of buildings, try to turn off some of the shadow casting options in the P3D graphic settings page, it's possible that what is flickering are shadows, because you turned everything on on that page.
In any case, did the problem happened with previous P3D version ? Because nobody ever reported it before, so perhaps it's a bug introduced with 2.4.
-
For what it's worth, I am also having this issue. Tried clearing out my shaders and this had no effect on the flickering buildings.
If you are referring JUST to the flickering of buildings, try to turn off some of the shadow casting options in the P3D graphic settings page, it's possible that what is flickering are shadows, because you turned everything on on that page.
In any case, did the problem happened with previous P3D version ? Because nobody ever reported it before, so perhaps it's a bug introduced with 2.4.
Could you suggest the specific shadow options which I should turn off. I am a bit reluctant to turn off shadow options because shadows are quite a nice visual. But I can do so if it helps to figure out what the problem is!
Yes, I had this problem since purchasing P3d V2. I think I started off with 2.0 but I can't remember exactly!
Thanks for the advice, looking forward to your reply!
-
And just a quick report... with all shadows turned off I still get flickering building textures.
-
And just a quick report... with all shadows turned off I still get flickering building textures.
An ALL of them ? Or just specific parts ? And, did it worked with P3D 2.3 and earlier version ?
-
And just a quick report... with all shadows turned off I still get flickering building textures.
An ALL of them ? Or just specific parts ? And, did it worked with P3D 2.3 and earlier version ?
Yes, every shadow category was turned off. I just recently purchased LSZH, but have had issues with EDDB (different scenery developers, I know) and a couple others... so this may be a native P3D issue but I can't be sure. The flickering has been around for quite some time, long enough that I can't remember which version I first noticed it with.
-
I have now again the V2.4 Compline reinstalled with the full installer of LM.
Unfortunately for me, the flickering is still even when switched off shadow as Skiflyzander.
The lights hovering still in the air.
Thanks for the help.
Urs Roth
-
I know that you guys aren't the developers of ENGM, but that product also has flickering issues... seems to be the transparent glass that is flickering. It's most noticeable (at LSZH) at terminal E pretty much on every texture, and Terminals A & B on some windows and some shadows. I really think this has got to be a P3D specific problem but who knows, because the navigation menus also flicker. Alright, I'll pipe down ^^ Not trying to be a pain. Awaiting your reply :)
-
I have this problem only at the airports from FSDT. But with the glass is also noticed.
Thanks for pointing skiflyzander. ;)
Hovering with you the lights too?
-
okay, so here is a little video showcasing the actual problem:
-
I know that you guys aren't the developers of ENGM, but that product also has flickering issues... seems to be the transparent glass that is flickering. It's most noticeable (at LSZH) at terminal E pretty much on every texture, and Terminals A & B on some windows and some shadows.
Ok, this is useful to know.
-
This is precisely the problem !!
What is the solution of FSDT?
-
This is precisely the problem !!What is the solution of FSDT?
You have reported two problems:
1) the flickering buildings. This seems to be a new problem introduced with 2.4, because nobody ever reported it before. There's obviously no solution right now, since 2.4 has just been released, but it WILL be looked at.
AND
2) "raising lights", which I still don't understand from your description and for your very unclear screenshots, if what you are seeing is the NORMAL raising of runway lights because they ARE raised (A BIT!!), both in real life and in the scenery to PREVENT visual, problems, or you are seeing something different. THIS other problem is not a problem, if they are raised a bit, but if they are raised a lot instead, it doesn't happen, nobody else has reported it before, and it surelly cannot change in any way with a "Restart Couatl" because, in Zurich, runway lights are NOT handled by Couatl, they are 100% standard AFCAD runways lights, and Couatl doesn't handle them in any way.
-
Okey then I look further.
That's not true with the flickering of the buildings.
I have this for version 2.3. I have mentioned this here on 21/09/2014. There was 2.4 for the moment.
best regards
Urs Roth
-
There's obviously no solution right now, since 2.4 has just been released, but it WILL be looked at.
Excellent, thank you!
-
Problem found and fixed with the latest Live Update. No need to reinstall anything, just check for updates from the Couatl powered products menu, and let it perform the update.
-
Well, I just tried running the update from inside Prepar3d V2 and that didn't fix anything. Terminal E is still flickering like mad. Am I missing something?
-
Well, I just tried running the update from inside Prepar3d V2 and that didn't fix anything. Terminal E is still flickering like mad. Am I missing something?
There might be a permissions problem modifying the objects ( the upgrade works in a way that it patches the objects in real time, if you run under P3D ), if your P3D installation resides under the default C:\Program Files (x86)\ path.
In more recent sceneries like JFK 2, CYVR or KIAH, we used the C:\ProgramData\Virtuali path to store objects , so we can patch them on the fly without permission issues, but doing this for Zurich would require modifying the whole files structure, changing the installer, and ask to all users to redownload the whole installer, just to change ONE bye in two objects...
If you install P3D into a folder you created yourself, such as C:\Prepar3D V2, you won't have such issues, that's why it's usually suggested to install the sim into a folder OUTSIDE the C:\Program Files (x86) which your user account can't write.
You can fix this in several ways:
- Change Properties for the P3D\fsdreamteam\Couatl\Couatl.exe in the "Compatibility" page, to "Run as Administrator".
OR
- Change the permissions for the main P3D folder and subfolders, to give write permission to your user account. You do this by right-click on the P3D root folder, select "Security", then allow the account with your own user name to have Write or Full Controll access to that folder.
OR
- Turn down or off the UAC settings.
-
Super now everything works without flickering.
Great, fast and super work thanks!
Only my people running yet return value.
best regards
Urs Roth
-
Unfortunately, the problem is not completely solved by the flickering
I have now installed LSGG and in LSSG and LSZH it flickers again
regards
Urs Roth
-
Alright, so I went through and changed the permissions of my P3D folder as suggested, updated couatl within the sim and still have the problem. Maybe it's time for me to send my log file? To be honest I have no idea where it is as this is my first adventure trying to figure out an issue like this :D Just let me know what the next step should be and I'm happy to help! BTW... what's UAC? I'm a true newb at this.
-
I have again a question to the Lights
Who I've Switzerland Pro installed, the RWY lights are again out of sight. But when I turned off its per the SCEN part of CH are the lights back.
Do you have a solution?
best regards
Urs Roth
-
Alright, so I went through and changed the permissions of my P3D folder as suggested, updated couatl within the sim and still have the problem. Maybe it's time for me to send my log file?
I can only confirm that, if you follow the previous suggestions, the problem will be fixed, as was also confirmed by Ursli80, who also had the issue, and said it was fixed with the update.
To be honest I have no idea where it is as this is my first adventure trying to figure out an issue like this
Enable logging from the Troubleshooting section of the GSX Settings menu, and then restart FSX, go to Zurich, and exit. Check the %APPDATA%\Virtuali folder for a file named Couatl.log, and post it.
-
Unfortunately, the problem is not completely solved by the flickering
I have now installed LSGG and in LSSG and LSZH it flickers again
regards
Urs Roth
Maybe you missed this post? All I can say is that I have tried the suggested methods and nothing has worked yet.
-
Maybe you missed this post?
He first said the flickering WAS fixed so, obviously, something HAS changed after applying the latest Live Update so, the only possible explanation, is that he did something else when reinstalling the sceneries.
Or, maybe, he was referring to LSGG and we haven't done anything on LSGG yet so, but even if there's a need to fix LSGG, it's not possible that installing LSGG would Undo the LSZH which WAS fixed, unless something went wrong in the download of the files (like firewall or antivirus blocking), so the reinstall of LSZH LSGG has "downgraded" the Live Update.
That was a reason why I haven't suggested to reinstall anything, but JUST apply the Live Update, in order to minimize the chances to mess things up.
Maybe you missed this post? All I can say is that I have tried the suggested methods and nothing has worked yet.
I confirm that it should work with one of the two methods proposed, but you still haven't provided with the Couatl.LOG I've asked, so I can't possibly know why is not working on your system.
-
I actually don't have GSX installed into Prepar3d... is there any other method of getting a log to you?
-
hello
I would once again like to mention something.
First I had P3D v2.4 completely reinstalled.
2 I have the FSDT all installed last. (GSX, LSZH, LSGG)
3 When I installed and tested by GSX LSZH was all good.
4 Then I LSGG installed and then I again found Flickering glass panels on the vehicles and. On the buildings at the Gates Signs When large gate E Glass front but I have nothing except Gates signs.
I've mentioned in a post something with CH-Pro and RWY lighting you know there may be a solution? It's about:
I have CH Pro installed I had (LSZH, LSGG) RWY lighting no longer with the FSDT airports. If I take away the part of the hoes at CH-Pro Scen in the Sceneryen are the lights back.
Would be grateful for help.
best regards
Urs Roth
-
I actually don't have GSX installed into Prepar3d... is there any other method of getting a log to you?
Yes, but it's a bit tricky. Why you don't just install it ? It's free to use at all our airports, and if you don't install it, you'll lose some scenery features, like docking systems.
-
3 When I installed and tested by GSX LSZH was all good.
Of course it was.
4 Then I LSGG installed and then I again found Flickering glass panels on the vehicles and. On the buildings at the Gates Signs When large gate E Glass front but I have nothing except Gates signs.
Nobody said that fix would do anything for LSGG, so it's just normal. I guess we would need a separate fix for it too.
I have CH Pro installed I had (LSZH, LSGG) RWY lighting no longer with the FSDT airports. If I take away the part of the hoes at CH-Pro Scen in the Sceneryen are the lights back.
Is the scenery coming with its own AFCADs ? If yes, perhaps there's a conflict, since runway lights come with AFCADs.
If no, that might indicate an altitude problem in that area, so the CH Pro mesh is covering the lights at LSZH, even if it's just a bit, try to see if you see any difference with different mesh resolution settings.
-
Alright, here is the log file!
Using airport customization from GSX.airports.lszh_fsdt
Patching for ZWriteAlpha in file model/LSZH_ED_TME.mdl 0
Patching for ZWriteAlpha in file model.LSZH_ED_TMCTR/LSZH_ED_TMCTR.MDL 0
disconnected from SimConnect.
-
There's nothing wrong with the .LOG file, but I need you to do another test:
- Reinstall Zurich using the current installer
- Take a Couatl.LOG of the FIRST run, after the installation
-
Patching for ZWriteAlpha in file model/LSZH_ED_TME.mdl 0
Patching for ZWriteAlpha in file model.LSZH_ED_TMCTR/LSZH_ED_TMCTR.MDL 0
Airport cache regeneration warnings:
CreateFileMapping failed because the file has size 0 (system:0) accessing BGL file C:/Program Files (x86)/Lockheed Martin/Prepar3D v2/Addon Scenery/ULLI_Pulkovo_Reload_FSX/scenery/0_LS_Neva_VTPX.BGL, file ignored
CreateFileMapping failed because the file has size 0 (system:0) accessing BGL file C:/Program Files (x86)/Lockheed Martin/Prepar3D v2/Addon Scenery/ULLI_Pulkovo_Reload_FSX/scenery/LS_Neva_LWM2.BGL, file ignored
CreateFileMapping failed because the file has size 0 (system:0) accessing BGL file C:/Program Files (x86)/Lockheed Martin/Prepar3D v2/Addon Scenery/ULLI_Pulkovo_Reload_FSX/scenery/LS_Neva_VTPL.BGL, file ignored
CreateFileMapping failed because the file has size 0 (system:0) accessing BGL file C:/Program Files (x86)/Lockheed Martin/Prepar3D v2/Addon Scenery/ULLI_Pulkovo_Reload_FSX/scenery/LS_Neva_VTPP.BGL, file ignored
Warning: airport ENGM described in multiple BGL files without proper DeleteAirport record
Airport cache regeneration completed with success in 10 seconds
Loading airport LSZH from C:/Program Files (x86)/Lockheed Martin/Prepar3D v2/FsDreamTeam/ZurichX/scenery/APX_LSZH.BGL
Using airport customization from GSX.airports.lszh_fsdt
disconnected from SimConnect.
-
CreateFileMapping failed because the file has size 0 (system:0) accessing BGL file C:/Program Files (x86)/Lockheed Martin/Prepar3D v2/Addon Scenery/ULLI_Pulkovo_Reload_FSX/scenery/0_LS_Neva_VTPX.BGL, file ignored
CreateFileMapping failed because the file has size 0 (system:0) accessing BGL file C:/Program Files (x86)/Lockheed Martin/Prepar3D v2/Addon Scenery/ULLI_Pulkovo_Reload_FSX/scenery/LS_Neva_LWM2.BGL, file ignored
CreateFileMapping failed because the file has size 0 (system:0) accessing BGL file C:/Program Files (x86)/Lockheed Martin/Prepar3D v2/Addon Scenery/ULLI_Pulkovo_Reload_FSX/scenery/LS_Neva_VTPL.BGL, file ignored
CreateFileMapping failed because the file has size 0 (system:0) accessing BGL file C:/Program Files (x86)/Lockheed Martin/Prepar3D v2/Addon Scenery/ULLI_Pulkovo_Reload_FSX/scenery/LS_Neva_VTPP.BGL, file ignored
You have some problems here, but they won't affect any of our products, it's just that you have several corrupted files.
Patching for ZWriteAlpha in file model/LSZH_ED_TME.mdl 0
Patching for ZWriteAlpha in file model.LSZH_ED_TMCTR/LSZH_ED_TMCTR.MDL 0
This IS a problem. Are you SURE ( really sure! ) this log was produced on the FIRST startup of the sim, as soon as you installed Zurich ? Because, on a freshly-reinstalled Zurich, this line shouldn't end up with a 0, but with a number. It's OK if it ends with 0, but ONLY after the 2nd run of the sim.
So, please be entirely sure. If you are not, or you don't remember, try the following:
- Uninstall Zurich. Be sure you don't have the Simobject\FSDT_LSZH folder anymore
- Reinstall Zurich, be sure you use the current installer.
- Do another log, and post JUST the last lines, everything else is not important.
-
Alrighty then, followed your directions to a tee and here is the log:
Starting system monitors
Current locale is English_United States.1252
SharedMemInterface connected
GSX is in trial mode (state=0, activation=-25006)
Loading aircraft data from Airplanes\Aerosoft Airbus A319 CFM
intelliscene.cfg provides aircraft data with priority 1
aircraftDb.py provides aircraft data with priority 2
Using aircraft data from aircraftDb.py
Found gsx.cfg file at C:\Users\Nicholas\AppData\Roaming\Virtuali\Airplanes\Aerosoft Airbus A319 CFM\gsx.cfg
Patching for ZWriteAlpha in file model/LSZH_ED_TME.mdl 0
Patching for ZWriteAlpha in file model.LSZH_ED_TMCTR/LSZH_ED_TMCTR.MDL 0
Starting new persistent timer 'ZurichX'
Airport cache regeneration warnings:
Warning: airport ENGM described in multiple BGL files without proper DeleteAirport record
Airport cache regeneration completed with success in 20 seconds
Loading airport LSZH from C:/Program Files (x86)/Lockheed Martin/Prepar3D v2/FsDreamTeam/ZurichX/scenery/APX_LSZH.BGL
Using airport customization from GSX.airports.lszh_fsdt
disconnected from SimConnect.
-
hello
I do not know if CH-Pro has its own AFCAD. During installation, it is specifically mentioned in your products.
Can I find out? When such?
I have to correct. The PAPI lights (which change from red to white) are each always to see whether CH Pro Scen is on or off.
Please let me know s when a solution is available because of the flickering for me. But which is much better. Thanks again for that.
Best regards
Urs Roth
-
I do not know if CH-Pro has its own AFCAD. During installation, it is specifically mentioned in your products.
You must have confused this with the FS9 version, which had an alternate installer with different colored textures to match the FS9 version of CH Pro.
None of this is relevant with the FSX version, both because the FSX CH Pro doesn't have that ugly green/pink colors anymore, so we don't need to provide with unrealistic textures to match it anymore, but also because we never tested the FSX version of Zurich with CH Pro, users can use the Trial version we offer to assess compatibility with their other add-ons.
Can I find out? When such?
Probably using the FSX Airport Scanner program, to search for any other AFCAD for Zurich.
I have to correct. The PAPI lights (which change from red to white) are each always to see whether CH Pro Scen is on or off.
Not understand you here.
Please let me know s when a solution is available because of the flickering for me. But which is much better. Thanks again for that.
The flickering problem is solved at Zurich, we'll have to made a separate fix for Geneva, but I still can't see any problems with any of the lights.
-
Patching for ZWriteAlpha in file model/LSZH_ED_TME.mdl 0
Patching for ZWriteAlpha in file model.LSZH_ED_TMCTR/LSZH_ED_TMCTR.MDL 0
If you are REALLY sure this log has been produced immediately after you installed Zurich, using the CURRENT version of the installer, than it's clear why it's not working: the patching hasn't been made.
Now, since it clearly works, the only possible explanations left are:
- You haven't produced this log after the FIRST FSX restart following the Zurich Uninstall/Reinstall process.
OR
- You haven't manually removed any file that was eventually left in the Simobjects\Misc\FSDT_LSZH folder
OR
- You are not using the latest version of Zurich.
That "0" in the line, means the patching is working, but the file to be patches is either ALREADY patched (but in that case you shouldn't see the flickering) OR it's not the as it's supposed to be before the patching, that would seem to indicate a different version of the scenery.
Just to be entirely sure, I just removed Zurich on my system, and reinstalled it, and this is what my log shows:
Patching for ZWriteAlpha in file model/LSZH_ED_TME.mdl 1
Patching for ZWriteAlpha in file model.LSZH_ED_TMCTR/LSZH_ED_TMCTR.MDL 1
Of course, no flickering whatsoever on the glass.
-
Okay, I might need a walkthrough to uninstall this. Sorry about that, but i must be doing it completely wrong.
Here is how I did it last time:
De-activated LSZH
Uninstalled LSZH
left GSX and Coutal(think I spelt that wrong) in place
reinstalled LSZH (downloaded the installer from the LSZH product page)
Fired up the sim and activated LSZH
Closed the sim and that's the log file I attached
I must be missing something here because if it works for you, I must be doing something very wrong!
-
Here is how I did it last time:
De-activated LSZH
Never said you had to do that. Won't matter if you did, but it's useless and it's just a loss of time.
I must be missing something here because if it works for you, I must be doing something very wrong!
It seems you have skipped this step, which I indicated in two of my previous replies:
- Uninstall Zurich. Be sure you don't have the Simobject\FSDT_LSZH folder anymore
You haven't manually removed any file that was eventually left in the Simobjects\Misc\FSDT_LSZH folder
-
Are you talking about the FSDT_ZurichX folder in appdata because the FSDT_LSZH folder doesn't exist after uninstalling ZurichX...
-
Are you talking about the FSDT_ZurichX folder in appdata because the FSDT_LSZH folder doesn't exist after uninstalling ZurichX...
The one under the FSX\Simobject folder.
The one under %APPDATA% it's always empty and doesn't matter (it's created by FSX itself).
It's normal you wouldn't see that folder anymore under the FSX\Simobject folder, because the uninstaller removes it, mine was just an EXTRA precaution to be entirely and absolutely sure you were starting from a clean situation.
But as I've said, I really don't have an explanation why the patch is not successful. It's not that is not running correctly, because it is, it's just that it reports your objects were EITHER already patched (but you shouldn't see any flickering in that case), or they are not as they are supposed to be in the current version of the installer, so they are not patched for that reason.
Would you like to try a Teamviewer connection, so I can have a look at your system ? PM me to arrange that.
-
Hello
With the PAPI lights I meant the 4 lights which are mounted respectively on the left of the runway which change from red to white and vice versa, depending on the height.
These are always watching even if I have activated in Switzerland Pro X the X Switzernald Scen folder or not.
I have the problem, that of whom I is turned on no longer have the lights of the runway. And wen it is off, I have re-firing.
And just as mentioned, the so-called PAPI lights are to be seen whether I have turned on or off to Switzerland X Scen folder.
best regards
Urs Roth
-
Hey just sent you a PM and didn't see it in my outbox, so I just wanted to check and make sure you saw it!
-
With the PAPI lights I meant the 4 lights which are mounted respectively on the left of the runway which change from red to white and vice versa, depending on the height.
Of course I know what they are, I asked what the problem you were having with them.
These are always watching even if I have activated in Switzerland Pro X the X Switzernald Scen folder or not.
I have the problem, that of whom I is turned on no longer have the lights of the runway. And wen it is off, I have re-firing.
I still don't understand you. I can see working PAPI lights at Zurich, see the attached screenshot.
-
Hello
Yes exactly what I meant these lights. But these are not the problem they are always available
I sent you a picture attached which lights I do not see who I Schwitzer country X Pro. (Scen folder)'ve switched.
Sorry I could myself make any since I'm at work.
greetings
Urs Roth
-
Yes exactly what I meant these lights. But these are not the problem they are always available
Now it becomes very confusing: since you don't have any problems with PAPIs, why start a discussion about them ?
I sent you a picture attached which lights I do not see who I Schwitzer country X Pro. (Scen folder)'ve switched.
So, you are now saying that, if you switch ON the CH Pro scenery, you lose the main runway approach lights ? If this is the case, I can't see how this could have anything to do with the scenery. Do they work together in FSX ?
-
Since you have misunderstood something. Or am I wrong words. Maybe it is because I have to work with Google translator. Excuse these problems.
The one with the PAPI lights I have only mentioned because they are always visible without problems. Only the main runway lighting causes problems, as you have mentioned it.
No I have been using for about 2 months now with P3D version 2.4
best regards
Urs Roth
-
No I have been using for about 2 months now with P3D version 2.4
Ok, now I understood you. Yes, the online translator must have confused the meaning of your sentence. So, you never used Zurich + CH Pro, before installing P3D ? Never tried them with FSX ?
I'm sorry but, if the problem goes away by turning off CH Pro, there's not much we can do from our side. As I've said, we only tested the old version under FS9, but can't guarantee anything with the FSX/P3D version. That's why we have Trial versions for: so you can test the scenery compatibility with other add-ons you might have.
But I would be interested to know if the problem happened in FSX too, assuming you tested it under FSX. If not, maybe someone else that tried it could confirm it.
-
Sorry again the translation problem.
So in FSX I had the scenery and the airport of AS together without problems in operation.
I would have to ask someone who has already installed FSX.
Would this help you?
greetings
Urs Roth
-
So in FSX I had the scenery and the airport of AS together without problems in operation.
So that answers the question, we are also having problems with Geneva and P3D lights, and it's definitely a bug that has been introduced with 2.3 or 2.4, because there wasn't any problem up to 2.2, so we reported it to Lockheed Martin, there's nothing we can do right now, other than waiting for a fix on their part.
-
Good day
So a friend of mine has this been tested in FSX with the trial version of FSDT Zurich X.
He's there all the lights and lights of the runway.
Personally, I used to FSX times unfortunately the AS version of Zurich and this went well also.
Does this help you a little?
best regards
Urs Roth
-
Excuse my message from before.
Thank you for your inquiries and work.
greetings
Urs Roth
-
Hey just an update. Updating from nvidia 344.11 to the latest driver solved the flickering issues. No longer having this problem at lszh and ltba is also not having this issue anymore! :)
-
Good to know. Since P3D use the video card way more than FSX ever did (which is good), the downside of it, is that it's more dependent on the video drivers not having bugs.