De nombreuses questions ont peut-être déjà trouvé une réponse dans notre base de connaissances. Consultez-la pour obtenir vos réponses avant de nous contacter. Base de connaissances
À propos de X-Plane.to
X-Plane.to est votre plateforme de choix pour les add-ons, mods et livrées de X-Plane 12. Qu'ils soient payants ou gratuits : Nous les couvrons tous. A propos de nous
Hi, I'd guess you're talking about reflections of the ground that are showing up on the cockpit windows? If so, this is an unfortunate side-effect of the "Enhance Global Illumination" technique and until XP12.1 there is not much workaround but to disable the feature. You'll still get better than default cockpit illumination without, but not as bright as with it.
Hi, is this the exact message? In any case, I'd suggest you enable the FWL "debug" mode, then reload all scripts, and once the error message shows up, use the FWL menu to save the debug log to file. This should contain more information about this issue, with eventually the script line of code causing the problem if any.
If the effect is too strong visually, you could opt to disable the "Enhance Global Illumination" setting. The script will enhance visuals better than default still, although not as much as with GI, but without these side effects.
Hi, when flying at a higher altitude with clear sky, it is possible it gets a little bit bluer, this is an unfortunate (though managed to some extent) side effect of "bending" the limitations of XP12 rendering code. Nevertheless, this can also be exacerbated if the cube map is not updated properly, which unfortunately XP12 is also suffering from. The script is offering the "Auto Update IBL" setting in order to forcefully ensure XP12 is updating the cube map from which it renders/tint the lighting, though this option might induce from light to moderate fps hit depending on your hardware and the complexity of the environment you're flying into.
Thank you for the video, this is helping. It seems to me the script is not applying some of the changes (as seen by the bigger light at night which shouldn't look like the default). I'd suggest you first try the latest (v1.9.1 updated a couple days ago) because it changes the way it is handling datarefs in order to workaround a strong limitation in the way FWL is handling datarefs (they are not local to the script and can collide with other scripts). This should prevent any possible conflicts with other scripts (hoping). Then I'd suggest you follow the "debugging" procedure which I've posted above. It is the procedure which is explained in the FWL Manual and should help finding out what this issue could be (if related to FWL). Last but not least, I'd try without any other plugins in order to cross check whether one of these is a source of conflict.
I've cross-checked and I can't repro. Could it be you're using other scripts and this is interfering?
PS: there could be incompatibility issues when using other scripts that are trying to also write same datarefs. This is a FWL limitations only. I've a pending update that cures this issue and which might cure the issue you are reporting eventually.
Hi, it appears this is a FlyWithLua limitation. In short, it prevents two scripts from registering a write dataref twice... even if only one will be actually writing the dataref at run time. I'll certainly raise the issue to the developer but in the meantime you can abuse FWL and workaround the issue in manually editing the rxp-xp12-enhancer.lua script:
Add a ", -1" at then end of line 550 like this:
if XPLMFindDataRef(name) ~= nil then dataref(var, name, writable and "writable" or "readonly", -1) end
This warning message is meant to only remind the script might not be fully compatible with newer versions, because it is essentially modifying private art datarefs which might not be working the same or not at all in any future version. These private art datarefs are first and foremost meant for LR internal use only, but most of the time it will be safe to use the script, and most of the time it will also work the same. Only sometimes the script might not work as expected. Mind you: the next XP12 update (v12.10+) will probably break a number of the "rendering" related options that this script provides, because it shall be an XP12 update mostly providing graphical an rendering changes.
If not, FlyWithLua will display an error message at the top. Otherwise, it should be safe to assume the scripts loads ok! Now should you manually edit the script to prevent the popup window to show up automatically, you could open the popup window from the FlyWithLua menu.
I suspect the crash isn't related to the script all by itself, because AFAICT a lua script can't make XP12 to crash. It is possible there is an error with FlyWithLua though, or another plugin might be 'chocking' when trying to do something with private datarefs which are also changed by the script. As a matter of fact, I've been running the current script without any issue with XP12.08r1 (please note it runs but I'm preparing a new version of the script with a few small changes for when 12.08 is officially released)
XP12.08 is only a beta for now, and this mod is released for official X-Plane release versions only (like with any previous version of this mod), because X-Plane beta versions are continuous work in progress and can break the mod anytime.
I didn't include a "preset" function because this script is still surfing on a moving XP12 target, where many things are changing between versions, and could render some of the settings completely obsolete. However, the script file itself is laid out in such a way that it should be easier to setup your favorite settings when it loads. I believe the nature of these settings mean they'd usually be set once for all, and only a few of them are actually session and/or aircraft dependent.
In other words, you might want to open the script file in a text editor and see the available options near the top. You can edit the settings (true or false value) and these will be the default values when the script loads. Eventually, you can always make multiple copies of the script, each with its own set of divergent settings, and globally deactivate each copies but one, using the global RXP_XP12E_DEBUG_DISABLE_ALL setting which is located above all. Whenever you want to change which script, hence for preset to use, just globally disable the active one, enable the one you'd like instead, and select FlyWithLua "Reload All Scripts".
4,543 Karma
CptLucky
Hi, thank you for your kind words! I believe the latest 1.9.4 is offering exactly what you're looking for!
CptLucky
Hi, I'd guess you're talking about reflections of the ground that are showing up on the cockpit windows? If so, this is an unfortunate side-effect of the "Enhance Global Illumination" technique and until XP12.1 there is not much workaround but to disable the feature. You'll still get better than default cockpit illumination without, but not as bright as with it.
CptLucky
Update 1.9.3 fixes this issue!
CptLucky
Hi, thank you for the notice and details. There is indeed an omission in the script/distrib. A new update is coming in a few to solve this!
CptLucky
Hi, is this the exact message? In any case, I'd suggest you enable the FWL "debug" mode, then reload all scripts, and once the error message shows up, use the FWL menu to save the debug log to file. This should contain more information about this issue, with eventually the script line of code causing the problem if any.
CptLucky
If the effect is too strong visually, you could opt to disable the "Enhance Global Illumination" setting. The script will enhance visuals better than default still, although not as much as with GI, but without these side effects.
CptLucky
Hi, when flying at a higher altitude with clear sky, it is possible it gets a little bit bluer, this is an unfortunate (though managed to some extent) side effect of "bending" the limitations of XP12 rendering code. Nevertheless, this can also be exacerbated if the cube map is not updated properly, which unfortunately XP12 is also suffering from. The script is offering the "Auto Update IBL" setting in order to forcefully ensure XP12 is updating the cube map from which it renders/tint the lighting, though this option might induce from light to moderate fps hit depending on your hardware and the complexity of the environment you're flying into.
CptLucky
Hi, it looks like the server is back online!
CptLucky
Hi, it looks like the server is back online!
CptLucky
Hi, unfortunately all attempts to upload a file end up with a 404 error on x-plane.to servers. I've open a support ticket yesterday.
CptLucky
Thank you for the video, this is helping. It seems to me the script is not applying some of the changes (as seen by the bigger light at night which shouldn't look like the default). I'd suggest you first try the latest (v1.9.1 updated a couple days ago) because it changes the way it is handling datarefs in order to workaround a strong limitation in the way FWL is handling datarefs (they are not local to the script and can collide with other scripts). This should prevent any possible conflicts with other scripts (hoping). Then I'd suggest you follow the "debugging" procedure which I've posted above. It is the procedure which is explained in the FWL Manual and should help finding out what this issue could be (if related to FWL). Last but not least, I'd try without any other plugins in order to cross check whether one of these is a source of conflict.
CptLucky
Hi, I have no idea why, but FlyWithLua documentation details a procedure to find out.
If you are having trouble with a script being put into the "Scripts (Quarantine)" folder and you can’t find the reason follow this procedure to help:
Lua will stop and also create a FlyWithLua_Debug.txt file that hopefully you can now see your issue in the Dev Console.
CptLucky
Hi, did you by any chance activate "night vision" ? (SHIFT+N)
CptLucky
I've cross-checked and I can't repro. Could it be you're using other scripts and this is interfering?
PS: there could be incompatibility issues when using other scripts that are trying to also write same datarefs. This is a FWL limitations only. I've a pending update that cures this issue and which might cure the issue you are reporting eventually.
CptLucky
Hi, thank you for your kind words! I'll investigate and hope I can repro, then fix in a future update.
CptLucky
Hi, it appears this is a FlyWithLua limitation. In short, it prevents two scripts from registering a write dataref twice... even if only one will be actually writing the dataref at run time. I'll certainly raise the issue to the developer but in the meantime you can abuse FWL and workaround the issue in manually editing the rxp-xp12-enhancer.lua script:
Add a ", -1" at then end of line 550 like this:
if XPLMFindDataRef(name) ~= nil then dataref(var, name, writable and "writable" or "readonly", -1) end
CptLucky
Hi and thank you for your kind words!
This warning message is meant to only remind the script might not be fully compatible with newer versions, because it is essentially modifying private art datarefs which might not be working the same or not at all in any future version. These private art datarefs are first and foremost meant for LR internal use only, but most of the time it will be safe to use the script, and most of the time it will also work the same. Only sometimes the script might not work as expected. Mind you: the next XP12 update (v12.10+) will probably break a number of the "rendering" related options that this script provides, because it shall be an XP12 update mostly providing graphical an rendering changes.
CptLucky
Hi, do you mean whether the scripts load alright?
If not, FlyWithLua will display an error message at the top. Otherwise, it should be safe to assume the scripts loads ok! Now should you manually edit the script to prevent the popup window to show up automatically, you could open the popup window from the FlyWithLua menu.
CptLucky
Hi, this is explained in the accompanying readme.txt!
Please review the "Configuration" chapter for more information.
CptLucky
Hi, thank you for your kind words!
I suspect the crash isn't related to the script all by itself, because AFAICT a lua script can't make XP12 to crash. It is possible there is an error with FlyWithLua though, or another plugin might be 'chocking' when trying to do something with private datarefs which are also changed by the script. As a matter of fact, I've been running the current script without any issue with XP12.08r1 (please note it runs but I'm preparing a new version of the script with a few small changes for when 12.08 is officially released)
CptLucky
Hi, thank you for your comment!
XP12.08 is only a beta for now, and this mod is released for official X-Plane release versions only (like with any previous version of this mod), because X-Plane beta versions are continuous work in progress and can break the mod anytime.
CptLucky
Thank you for your kind words!
I didn't include a "preset" function because this script is still surfing on a moving XP12 target, where many things are changing between versions, and could render some of the settings completely obsolete. However, the script file itself is laid out in such a way that it should be easier to setup your favorite settings when it loads. I believe the nature of these settings mean they'd usually be set once for all, and only a few of them are actually session and/or aircraft dependent.
In other words, you might want to open the script file in a text editor and see the available options near the top. You can edit the settings (true or false value) and these will be the default values when the script loads. Eventually, you can always make multiple copies of the script, each with its own set of divergent settings, and globally deactivate each copies but one, using the global RXP_XP12E_DEBUG_DISABLE_ALL setting which is located above all. Whenever you want to change which script, hence for preset to use, just globally disable the active one, enable the one you'd like instead, and select FlyWithLua "Reload All Scripts".
CptLucky
Thank you for your kind words! A new version tested with XP12.07 is now available!
CptLucky
Thank you for your kind words!