You’ll need to turn off team create if you’re uncopylocking it.
To my knowledge this is only true for Future lighting, which is not the intended usage of this plugin.
2 Likes
It’s not. Shadowmaps’ shadow calculation time nearly linearly scales with the number of lights in the scene. You can clearly see it on the microprofiler.
This is false too. I literally posted a scene with 8400 lights in it. Stop please.
12 Likes
The shadows for ShadowMap are not affected by scene lights, only the sun light. There is minimal performance impact. I have tested this by making 50k pointlights in a dense scene and observed effectively no change in average frame time:
With lights:
Baseline:
Only Future has severe performance implications with light sources.
If I enable shadows, increase the number and the range to max, and dramatically increase the density, there is a chug when you enter the lit area such that the lighting chunks render for the first time (i.e. the pop-in), but I’m skeptical this plugin will generate a dense enough light field that this will have any significant effect. I’m talking about tens of thousands of lights in the same small area.
7 Likes
I might try this. Since I know a decent amount of scripting but no lighting, if anything goes wrong, I would be happy to help.
Looks like this is a bug, can anyone report this? It happened after I clicked the plus button in plugin management.
Anyways, I started installing it, and…
I think you forgot that local plugins don’t run as scripts.
So, I tried the plugin model. Now, I still got the same thing in the output. I’m not really good at plugins so I might’ve not removed it properly, but the icon showed up.
When I tried baking this region, it just kept on spamming “Aborting!” in the output.
It made studio lag, so I had to restart it.
I tried it again, and this time, the create probes button worked.
And, it did add the lights after clicking bake. But they weren’t visible at that area, so I did another area.
I decided to do this spot, as it was dark.
I changed down the grid size and changed up the number of samples, each of them was on their min/max value.
I clicked create probes. It did quite a good job here:
I clicked bake and then it started spamming aborting again!
So, I just closed the output because this place won’t save.
After testing a few things, it looks like it won’t work on terrain, which is a major downside of this. It spams “Aborting!” when there’s terrain.
So, I was able to bake the probes of that area, and this is how it looks:
There is absolutely no light coming from them whatsoever.
looks like someone forgot to do tonumber()
I figured out the lights have a brightness of 0, when it was actually set to 1. We all know this would be a tedious process without the help of the command bar, so I executed:
for _, obj in pairs(workspace.LamplightRTGI:GetDescendants()) do if obj:IsA("PointLight") then obj.Brightness = 1 end end
That made the lights have a brightness of 1.
This is the result:
As you can see, it did a good job here. In game, it looks like this:
Then, I changed my graphics quality up to 10:
The actual lighting isn’t bad, but the design of the plugin is.
All in all, I think you need to fix some of the errors in your plugin. There were several problems, and it wouldn’t be too painful for me to do this, but for new users they just might give a dislike. If I were you, I would put the project in beta.
So, if you want any more information on the bugs from me, I’d be happy to help.
Oh yeah, the output will crash studio if I open it.
1 Like
Okay so there is a bug in studio right now that requires you to have plugin debugging enabled to use parallel luau features. This is the error you are encountering. Enable that, restart studio, and try again 
1 Like
Doing so does not to have any change/effect on the plugin. The error still appears in the output, but the plugin seems to still run. Though the brightness of the lights is still set to 0.
1 Like
The error you’re seeing is the parallel luau failing to recognize the scripts. There isn’t anything wrong with the plugin, it’s a roblox studio thing. I have no idea why the fix doesn’t work for you, but it has worked for plenty of others
2 Likes
If I take the source .rbxmx from the plugin, put it into ServerStorage so the parallel scripts can’t run, and then save it as a local plugin, then it works fine.
It looks like the scripts are running before the main plugin is, causing them to error (before Studio recognizes them as code that can use parallel lua maybe? they could be running before the plugin context is even created, because the plugin is an instance in of itself), so you could solve this by either having a yielding loop at the top of the script that waits until some value is set, or by simply disabling the scripts and enabling them when the “Bake” button is clicked, or even creating the scripts at runtime, but I believe that would require script injection permissions.
1 Like
I could try starting with them disabled… I’ll try it.
Update: Does not work. The only way it can work is if studio plugin debugging is enabled. I’m sure roblox will fix it
This looks quite nice for crossroads in my opinion.
But what would happen if the materials were correct and weren’t plastic?
Well the materials are what shipped with the game?
Lamplight works with any material, though. Try it out
I’d suggest turning the initial scene lighting brightness up a bit - it’s very dark.
You can turn the lamplight brightness up but that’s not as accurate as just having more light to start with
1 Like
dude those meshes look AMAZING, if there is one and if im allowed to use them could you send me a link to a pack or anything that has those meshes? it would be really helpful for one of my games
you didnt update the download, where do i download 1.2
Got some surprisingly good results in my game, Rooms.
Specifically Depths boss fight.
and on future lighting.
9 Likes
Wowee!! Right now you’ll get even better results if you have a couple of source pointlights in the scene.