Not all shadows are as they are supposed to be when you place objects in the editor.
Someehwere under map or edit or something like that is an options called calculate shadows, in the top-bar menu of your terrain editor.
In the tabs like file edit etc / Data/Generate static shadows
Prompting that command does not always work/fixes the map).. it asks the engine to re generate the outdated / improper shadows done on the "editor version" of your map AND it could/should fix the "playable version" of your map (do note that the display discrepancies in the editor version does matter less IF it is fixed when you play it online).. but
if you playtest your map and see no issues, it might not be useful to do so ?!
The mechanic is simple: every object has a shadow or shadows generated from dynamic shadows engine and they have two outlets: the editor and the game being played.. if these are in conflict (map's lighting versus a particular light emitting doodad for instance)
then you get: the message and something wrong visually on your map (wrong in the editor OR wrong in the editor AND coming out wrong in game OR something wrong in game)..
This tool would be awesome if it was reliable (which it is not (on macOS at least) .. it spits out the message without cause or doesn't spit out when it should blablabla..)
not to mention fixing often means data mining :/ ...
These are often high settings considerations in any case.. if people play in low, they don't apply.. (personally my internet loves me playing/working on low settings only)
On the other hand, if you want full hd quality then it is imperative to fix before you use/publish :P
(to reap the video result it is the whole point)
As for getting that message in the editor, over and over if you don't fix .. if it doesn't impair your capacity to make the map then just ignore it (:
The process of this "new" generation (rather a re set) is not being guaranteed at all.. it could be argued that you should not ever do it in your work (safe) map.. (since the state of your map might "deteriorate from this action/process) ..
always make a copy, generate and then check/test,
if you can't see any problems then do it to your work map too (because yes having the editor display stuff "properly" and in sync with the game experience is "important" although nowhere near vital, since it is the result (the engine displaying the game) that matters, not your workstation or the map status spitting errors at you
What is static shadow? and why mine is outdated?!
anyone know?
Not all shadows are as they are supposed to be when you place objects in the editor. Someehwere under map or edit or something like that is an options called calculate shadows, in the top-bar menu of your terrain editor.
In the tabs like file edit etc / Data/Generate static shadows
Prompting that command does not always work/fixes the map).. it asks the engine to re generate the outdated / improper shadows done on the "editor version" of your map AND it could/should fix the "playable version" of your map (do note that the display discrepancies in the editor version does matter less IF it is fixed when you play it online).. but
if you playtest your map and see no issues, it might not be useful to do so ?!
The mechanic is simple: every object has a shadow or shadows generated from dynamic shadows engine and they have two outlets: the editor and the game being played.. if these are in conflict (map's lighting versus a particular light emitting doodad for instance)
then you get: the message and something wrong visually on your map (wrong in the editor OR wrong in the editor AND coming out wrong in game OR something wrong in game)..
This tool would be awesome if it was reliable (which it is not (on macOS at least) .. it spits out the message without cause or doesn't spit out when it should blablabla..)
not to mention fixing often means data mining :/ ...
These are often high settings considerations in any case.. if people play in low, they don't apply.. (personally my internet loves me playing/working on low settings only)
On the other hand, if you want full hd quality then it is imperative to fix before you use/publish :P
(to reap the video result it is the whole point)
As for getting that message in the editor, over and over if you don't fix .. if it doesn't impair your capacity to make the map then just ignore it (:
The process of this "new" generation (rather a re set) is not being guaranteed at all.. it could be argued that you should not ever do it in your work (safe) map.. (since the state of your map might "deteriorate from this action/process) ..
always make a copy, generate and then check/test,
if you can't see any problems then do it to your work map too (because yes having the editor display stuff "properly" and in sync with the game experience is "important" although nowhere near vital, since it is the result (the engine displaying the game) that matters, not your workstation or the map status spitting errors at you
:D .
i usually leave it until im ready to upload publically
Great info thx