Vite Code: https://hastebin.com/sivarerako.js
Vanilla(?) Code: https://hastebin.com/dafupizoru.js
#Switching bundlers messed up my lighting.
faint veldt
left is vite version, right is vanilla. vanilla is desired outcome
restive isle
Do you get any errors in the JS console?
faint veldt
Do you get any errors in the JS console?
no errors.
i think i should also note that the three.js version on my bundled website is 0.145.0 while on the other it was 0.140.2
if that makes a difference
restive isle
the code here looks identical, i assume there is something a bit more subtle going on
if you can share a demo we could probably investigate that way
Perhaps also try commenting out scene.environment in both versions, are they identical if you do that?
faint veldt
tried playing around with jsfiddle, but couldnt find a way to upload the models
https://github.com/WallyTube/cm-three-rp this is the full code for the vite project
https://github.com/WallyTube/cm-three-rp-old this is the code for the previous version of the project with the desired lighting
restive isle
these are looking the same to me – there was a difference in the earlier link in the pmremGenerator.fromScene arguments, fixed in the github repos, possibly it was just that?
faint veldt
that's so odd
running that exact code for me gives me this
also the arguments are matching in both instances
@restive isle thinking about it, when you ran the code from the vite repo, you probably had to use your own three.js modules. what version did u have?
restive isle
i ran yarn to install deps, looks like it grabbed [email protected]
restive isle
chrome on mac yeah!
faint veldt
quick unrelated question
tryna put this code on a live site
im getting 404 errors for the two models.
do i have to import/require them into my main.js to be able to reference them?
dk if the process is different for bundlers
faint veldt
chrome on mac yeah!
i honestly think this is a bug at this point
just ran it on my mac with safari, and it appears fine
ran it on a family member's windows laptop with firefox too and it worked
faint veldt
i honestly think this is a bug at this point
@solar fern apologies if you don't like pings, but this is starting to look like a visual bug with three.js
restive isle
Can you create a live demo and confirm that the same URL looks different on two browsers?