So I’m working on a map on Glacier in Forge and randomly my ability to generate the Lightmap disappeared. Holding down on the D-pad to generate lighting now acts the same as pressing it once, taking me directly into player mode with no “generating lighting” prompt. My lightmap budget has been exceeded for a while and at the point of this bug it happened to be 217% (I was waiting to lower that until the map was done. Also, if y’all have any tips on how to lower the lightmap by using certain blocks over others, that’d be greatly appreciated).
I have worked on multiple maps before with lightmap budgets that well exceed this 217% and have not had this same issue. So I’m wondering, is this bug caused by the lightmap budget, but not tied to any specific value? Or is there something else that might be causing this error?
i appreciate any and all attempts to help 
sometimes its a simple as saving the map and relaunching it if you haven’t tried that already. I have had glitches in the past where i would launch a forge match and my controller set up would change drastically. Maybe its even your controller itself ? Also lightmap doest get rid of your ability to generate lighting. I once made a map when h:5 forge came out that had 417% lightmap and it ran just fine… It just looked like garbage lol.
> 2533274884969133;2:
> sometimes its a simple as saving the map and relaunching it if you haven’t tried that already. I have had glitches in the past where i would launch a forge match and my controller set up would change drastically. Maybe its even your controller itself ? Also lightmap doest get rid of your ability to generate lighting. I once made a map when h:5 forge came out that had 417% lightmap and it ran just fine… It just looked like garbage lol.
Unfortunately I have tried that. I’ve relaunched the map multiple times, even “saved as” and launched again. None of it works. It’s not my controller, I can generate lighting on other maps just fine. Not even restarting the entire game fixes it. I have, since this post, lowered the lightmap down to a percentage at which it worked before but it still does not work. Thank you for the suggestions though and please keep them coming. If I can’t find a solution, my final option to fix this will probably be to just make everything one huge prefab and paste it on another map haha.
> 2533274846132190;3:
> > 2533274884969133;2:
> > sometimes its a simple as saving the map and relaunching it if you haven’t tried that already. I have had glitches in the past where i would launch a forge match and my controller set up would change drastically. Maybe its even your controller itself ? Also lightmap doest get rid of your ability to generate lighting. I once made a map when h:5 forge came out that had 417% lightmap and it ran just fine… It just looked like garbage lol.
>
> Unfortunately I have tried that. I’ve relaunched the map multiple times, even “saved as” and launched again. None of it works. It’s not my controller, I can generate lighting on other maps just fine. Not even restarting the entire game fixes it. I have, since this post, lowered the lightmap down to a percentage at which it worked before but it still does not work. Thank you for the suggestions though and please keep them coming. If I can’t find a solution, my final option to fix this will probably be to just make everything one huge prefab and paste it on another map haha.
Did you try turning off “Light bake” when spawning in something (It’s usually on by default in the object properties whenever you spawn in something that has the option to enable/disable it (E.G. Floors and rocks) . Turning it off could ease the problem of lightmap resources)
Turn light bake off on as many blocks as you can.
Anything you can’t see.
Anything that won’t have shadows cast onto them.
Anything super dark in color, that IS in shadows.
And during forge, turn off weather if you have high lightmap.
Thank you all for your suggestions, I tried all of them but in the end the problem, I believe, was that I had too many Lights on the map. This is stupid in that it was not a placement of a light that initiated this problem. Oh well, it’s fixed now. Thank y’all for the help!