So oddly enough, ive only had issues with these light orbs while using Mists of Tamriel. I will also add that this happens regardless if i checked or unchecked fake lights. Now im gonna have to do some testing...
When using Lux and Lux orbis, I have terrible light balls in whiterun when I see it from far, I hope this will fix it... gonna test on next dyndolod generation
I advise you to report them to Sheson. If you want to remove them until it you get a better solution, use tfc command (from console) to get closer and select the bulb to get the editorID (like on example screenshot) and add it to the file, if you don't know how, just give me the EditorID or show me the screenshot with the buld selected.
To not generate fake lights in childworlds like Whiterun etc., do not check the option "Fake lights child world" in the advanced mode options. The option is disabled by default.
https://dyndolod.info/Mod-Authors Whenever there are any kind of compatibility issues or problems with the tools or the LOD patch in the game, they should be reported on the official DynDOLOD support forum. Especially when users report visual issues in the comment section for a mod and the issue seems to be some kind of compatibility or issue with DynDOLOD or the patching process. Users should be directed to the official DynDOLOD support forum for support or to report the problem. The purpose of the DynDOLOD patcher is to create a working LOD patch automatically without users having to worry (much) about patches etc. In particular, try to avoid modding or making mods like things were done before 2014, like overwriting full models or LOD assets just by their path and filename. The mod author is not supposed to provide any DynDOLOD support and things are supposed to be automatic for the user as much as possible. Whenever coming across a problem and the initial reaction is to disable something - which is only a troubleshooting step - or to make elaborate workarounds to get something to work, it could mean the way LOD generation and DynDOLOD in particular works is not fully understood or that there is a bug or an unexpected situation that is not yet addressed - either in 3rd party mods or the tools or whatever else. Remember, DynDOLOD is a patcher to automatically generate a LOD patch. The LOD patch it generates is not supposed to require patching itself.
Reach out and describe the problem or issue with as much information as possible in order to discuss and to address it one way or the other. There should never be a case where users have to do elaborate workarounds or do things that are contradicting the official DynDOLOD documentation. This does not mean that the documentation or the way LOD is generated is always right. It means that there is a case that needs looking at and that needs to be discussed and solved whatever the source and reason of the problem.
Making workarounds/mods instead of simply reporting a problem as requested and practiced since a decade in order to have it properly addressed and fixed is wasting time and not really helpful.
I've already replied to someone that the best solution is to report the problem to you. I've added a comment on the description page to encourage users to do so.
This mod has two aims, to solve a temporary problem until you fix it and to allow players to enjoy their game right away and disable the effects they don't want without disabling everything.
Most users won't bother to create an account on step to report a problem or won't even know what you need to report it, if you want I can report regularly what I've gathered here. If you need more information than the EditorID, let me know and I'll add it.
https://dyndolod.info Modding the game and using tools like DynDOLOD requires rudimentary computer and modding skills, like general knowledge of folders, file types, how the game stores mods and assets and how to use a mod manager and using tools like xEdit, the ability to read documentation and follow instructions and the willingness to ask questions, report problems and provide feedback on the official DynDOLOD support forum for qualified help and advice and to improve the tools, processes and compatibility. https://dyndolod.info/Official-DynDOLOD-Support-Forum Report the actual problem or error message [..] Read the explanations and tips below, especially about what information and logs to provide and how.
If a problem is not reported it might not ever get fixed. The more problem reports to the appropriate forum/person the more likely a problem can be fixed properly and quickly. Specific logs, information etc. for an issue is requested on a case by case basis as troubleshooting progresses.
My posts are for a mod author that made a mod that "lets you disable the buggy lights generated by DynDOLOD FxGlow".
These bugs should be reported to the tool developer so they are actually fixed. I am linking/quoted the relevant official documentation that explains this in detail to mod authors. How is pointing out proper modding/development procedure not helpful?
If I get asked what information to provide when making posts on the official DynDOLOD support forum, I obviously link to the page that explains that. It directly answers the asked question. How is that not helpful?
I understand what you're saying, and appreciate the effort, but I believe Sthaagg already pointed it out: Most users won't bother to create an account on STEP to report an issue or know what to report. Fwiw, on my own personal setup, i'm running the same version of Dyn 3.0a and have not encountered the issue.
Sheson, no, your response doesn't help. I asked you what else was needed for you to be able to solve the error with the information available to me. You paternalistically referred me back to your documentation, which I have already read multiple times. If I took the trouble to contact you privately on Discord and ask you the question, it's because I couldn't find the answer in there.
As I have already told you, and as Magus80Mods has reiterated, most users will not create a STEP account just for this.
Moreover, from my point of view, since the problem is not present for everyone, it may not necessarily be a bug to be treated at the DynDOLOD level; it might be more of a user-specific issue.
On top of that, given the first post on the support forum with the messages highlighted in red redirecting to the documentation, it is highly likely that most people will give up even before posting.
I suggested centralizing this and asked you directly by Discord private messaage for more details precisely to help you resolve these cases.
You prefer to respond to me publicly, self-quoting your documentation, which, I'm sorry to say, is not always clear, especially for non-English speakers like myself and many others. This mod is only here to help people fix a problem in their own setup or to allow them to select what they want to keep or not; it doesn't use any resources from DynDOLOD.
You came here explaining in a paternalistic and moralizing tone that it's useless, and despite that, I offered to report the bugs and asked for clarification. You just reposted your documentation, citing a passage that essentially says if we don't have a minimum of skill, we shouldn't use it. When a user tells you it doesn't really help, you innocently reply that you don't understand the problem.
Perhaps you should reconsider your way of communicating. I have great respect for your work, and I believe I have some computer and modding skills, but I won't necessarily tolerate being looked down upon for a simple mod that just fixes a small problem. If you're offended by the term "buggy light," consider that your own wording is much worse.
Maybe it would have been easier for you to respond to me with what you needed? So, sorry for bruising your ego, and tell me what you require, or just leave this little mod in its corner since, according to you, it's useless and don't take advantage of the fact that I can report bugs reported by people who neither have the desire, patience, nor skills to do so.
A quick look on the DynDOLOD support forum shows that it does not matter what initial information a post contains, since whatever logs, screenshots or additional information is needed is simply requested anyways. It so happens that I already wrote detailed instructions on the official DynDOLOD website so I can simply link them as needed:
Do I need to re-write the explanations here so they become more helpful?
According to the image above, how to do useful screenshots is already known, but when making a post on the official DynDOLOD support forum it should screenshots that were made for the same LOD patch generation as the logs.
These two part are clear. I added the link for screenshots on the main page.
I don't know why my step accounts is disabled :/ I try to reactivate it without success, i will post the screenshots i receive here when it will be re-enabled.
Thank you so much for this Sthaag, I would not have known that the wierd lights were caused by a problem with Dyndolod & presumed it was something to do with Lux or some placement of lights due to the overhaul & would not have thought to let the Dyndolod folks know it was a problem. Its people like you finding the issue & reaching out to us "normal" mod users that highlight & explain what is going on with our games & then going to the trouble of making mods to help until the author of the original mod can change what needs to be changed that make this community of modders the helpful & friendly fellowship that it is.
I don't know which ones this fixes, but I've reported the ones I've found to sheson and he has fixed them. The last one I reported was dunmer lanterns in better tel mithryn, and sheson said that those will be fixed in the next alpha.
27 comments
If you don't know how, provide a screenshot like the one in description I will add them.
https://ibb.co/2qYzjL7
https://ibb.co/3cGvHHh
it's only in the lod when watching the city from outside... you can see them even during the day
If you want to remove them until it you get a better solution, use tfc command (from console) to get closer and select the bulb to get the editorID (like on example screenshot) and add it to the file, if you don't know how, just give me the EditorID or show me the screenshot with the buld selected.
screenshot
https://ibb.co/SxjfJ2q
[Forms|WhiterunLocation]
LuxOrbis_FarmEmberFireOmniNS_DynDOLOD_OBJECT|Empty_DynDOLOD_LOD
See https://dyndolod.info/Help/Advanced-Mode#Fake-lights and https://dyndolod.info/Help/Glow-LOD#Fake-Lights
In case of feedback, questions or problems with DynDOLOD, use the official DynDOLOD support forum for qualified discussions, advice and help.
Whenever there are any kind of compatibility issues or problems with the tools or the LOD patch in the game, they should be reported on the official DynDOLOD support forum. Especially when users report visual issues in the comment section for a mod and the issue seems to be some kind of compatibility or issue with DynDOLOD or the patching process. Users should be directed to the official DynDOLOD support forum for support or to report the problem. The purpose of the DynDOLOD patcher is to create a working LOD patch automatically without users having to worry (much) about patches etc. In particular, try to avoid modding or making mods like things were done before 2014, like overwriting full models or LOD assets just by their path and filename. The mod author is not supposed to provide any DynDOLOD support and things are supposed to be automatic for the user as much as possible.
Whenever coming across a problem and the initial reaction is to disable something - which is only a troubleshooting step - or to make elaborate workarounds to get something to work, it could mean the way LOD generation and DynDOLOD in particular works is not fully understood or that there is a bug or an unexpected situation that is not yet addressed - either in 3rd party mods or the tools or whatever else. Remember, DynDOLOD is a patcher to automatically generate a LOD patch. The LOD patch it generates is not supposed to require patching itself.
Reach out and describe the problem or issue with as much information as possible in order to discuss and to address it one way or the other. There should never be a case where users have to do elaborate workarounds or do things that are contradicting the official DynDOLOD documentation. This does not mean that the documentation or the way LOD is generated is always right. It means that there is a case that needs looking at and that needs to be discussed and solved whatever the source and reason of the problem.
Making workarounds/mods instead of simply reporting a problem as requested and practiced since a decade in order to have it properly addressed and fixed is wasting time and not really helpful.
I've already replied to someone that the best solution is to report the problem to you. I've added a comment on the description page to encourage users to do so.
This mod has two aims, to solve a temporary problem until you fix it and to allow players to enjoy their game right away and disable the effects they don't want without disabling everything.
Most users won't bother to create an account on step to report a problem or won't even know what you need to report it, if you want I can report regularly what I've gathered here. If you need more information than the EditorID, let me know and I'll add it.
Modding the game and using tools like DynDOLOD requires rudimentary computer and modding skills, like general knowledge of folders, file types, how the game stores mods and assets and how to use a mod manager and using tools like xEdit, the ability to read documentation and follow instructions and the willingness to ask questions, report problems and provide feedback on the official DynDOLOD support forum for qualified help and advice and to improve the tools, processes and compatibility.
https://dyndolod.info/Official-DynDOLOD-Support-Forum
Report the actual problem or error message [..] Read the explanations and tips below, especially about what information and logs to provide and how.
If a problem is not reported it might not ever get fixed. The more problem reports to the appropriate forum/person the more likely a problem can be fixed properly and quickly. Specific logs, information etc. for an issue is requested on a case by case basis as troubleshooting progresses.
These bugs should be reported to the tool developer so they are actually fixed. I am linking/quoted the relevant official documentation that explains this in detail to mod authors. How is pointing out proper modding/development procedure not helpful?
If I get asked what information to provide when making posts on the official DynDOLOD support forum, I obviously link to the page that explains that. It directly answers the asked question. How is that not helpful?
As I have already told you, and as Magus80Mods has reiterated, most users will not create a STEP account just for this.
Moreover, from my point of view, since the problem is not present for everyone, it may not necessarily be a bug to be treated at the DynDOLOD level; it might be more of a user-specific issue.
On top of that, given the first post on the support forum with the messages highlighted in red redirecting to the documentation, it is highly likely that most people will give up even before posting.
I suggested centralizing this and asked you directly by Discord private messaage for more details precisely to help you resolve these cases.
You prefer to respond to me publicly, self-quoting your documentation, which, I'm sorry to say, is not always clear, especially for non-English speakers like myself and many others. This mod is only here to help people fix a problem in their own setup or to allow them to select what they want to keep or not; it doesn't use any resources from DynDOLOD.
You came here explaining in a paternalistic and moralizing tone that it's useless, and despite that, I offered to report the bugs and asked for clarification. You just reposted your documentation, citing a passage that essentially says if we don't have a minimum of skill, we shouldn't use it. When a user tells you it doesn't really help, you innocently reply that you don't understand the problem.
Perhaps you should reconsider your way of communicating. I have great respect for your work, and I believe I have some computer and modding skills, but I won't necessarily tolerate being looked down upon for a simple mod that just fixes a small problem. If you're offended by the term "buggy light," consider that your own wording is much worse.
Maybe it would have been easier for you to respond to me with what you needed? So, sorry for bruising your ego, and tell me what you require, or just leave this little mod in its corner since, according to you, it's useless and don't take advantage of the fact that I can report bugs reported by people who neither have the desire, patience, nor skills to do so.
Read the https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs section to know which log and debug log to upload when making posts.
Read the https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots section to know how to provide a screenshot of an object with additional information when reporting problems.
Do I need to re-write the explanations here so they become more helpful?
According to the image above, how to do useful screenshots is already known, but when making a post on the official DynDOLOD support forum it should screenshots that were made for the same LOD patch generation as the logs.
I don't know why my step accounts is disabled :/
I try to reactivate it without success, i will post the screenshots i receive here when it will be re-enabled.
something to do with Lux or some placement of lights due to the overhaul & would not have thought to let the Dyndolod folks know it was a problem. Its people like you finding the issue & reaching out to us "normal" mod users that highlight & explain what is going on with our games & then going to the trouble of making mods to help until the author of the original mod can change what needs to be changed that make this community of modders the helpful & friendly fellowship that it is.
It is exactly why i created this :)