Upgraded to V3, issue still happens when I have the box height set really, like 3000-4000 studs high. All the meshes below a certain point wont render 
Settings:
Managed to find a way around it anyways, by rendering each height level separately so all the meshes would show up, but its a bit annoying. Thanks for making it render super fast though, does make the workflow a lot easier
Can you dm me with a studio file of that map or at least the island so I can debug what is going on?
Getting the same issue with a 35k x 2.6k x 18k map, it renders meshparts/unions that are high up in Y level but not any that are low down near the ocean (at y400) like this island. (The shadows are where stuff like hill meshparts and trees should be)
However after messing around with the code, trying different CollisionFidelitys, RenderFidelitys, plugin settings, raising the entire map in Y level, and more, I’m starting to think this is a roblox bug of some kind.
Hey! I used to render my maps with RoRenderV2 and, as soon as I needed to render a map of mine again, I wanted to try RoRenderV3. The issue here is: as soon as I create settings, a purple box spawns but with no draggers (corners and everything, just no draggers) and, when I try to close the plugin and try with the old pluign (V2) then the draggers just show up. Really weird, also tried to use the command to destroy it but doesn’t seem to work. Do you know how to fix this?
Thank you for reading!
I’m getting the 400 error to- could you share your updated code?
Turns out there is a studio bug with raycasting meshes with heights > 2000 studs. Will update the plugin to work around this issue tonight.
Thanks for your reports
@igoing2win
@vetexgames
@kni0002
Seems like I’m encountering an error again. Not too sure why considering it was working a few moments ago.
I am starting the server before running the studio server, and I’ve made sure to enable HTTP requests but it still seems to give me an error. This wasn’t happening a few minutes ago and I can’t figure out why it’s producing this error.
Disregard this message. I flushed my DNS resolver cache and it seems everything went back to normal.
I keep trying to start the server, however the button just turns a lighter blue and nothing changes. I have HTTPS enabled, and have the config settings loaded. Any help would be great
When the button turns blue that means that the server is started. You just follow the steps from there
I did, after a while, nothing changed within the RoRender UI, like the timer, rendered image, or percentage finished. Occasionally after trying to close the program it would freeze (“Not Responding”). It’s possible that my map is too big, but I don’t believe that would be the issue.
If the output image is above 16k x 16k then the program will crash
As I’m writing this I’m trying to render a small portion of the map using the default size when settings are first created, and I’m getting the same result. How long does it take on average to start the Render(or until the timer starts)? It could be a computer-based thing if it takes a few minutes, however I have a pretty good computer.
It start 5 seconds after you press run on the roblox client
that’s what I was missing, sorry I forgot to hit run haha.
I tried installing program on my Mac, it says that it is unsupported.
Its 13-inch, 2017 MacBook Pro with MacOS Ventura (latest) on it.
I tried opening it other way, it said app is damaged
[UPD] Found solution above. For others:
Download Source code and npm install electron into terminal (if not installed), then cd to folder of RoRender and type npm start to terminal. Also this instruction is located in README file.
Are you able to make a solution for RoRender V3? Ran into this issue
just curious as to what’s the absolute limit on map size? i’ve found myself needing to render a 61k by 33k stud map and it keeps returning an http error 500 so i’ve found myself having to split it into chunks
The map size is unlimited, the output image size is around 16k x 16k pixels
It keeps happening in the same place, and it seems to be whenever it gets to a larger portion of the map.
It seems to be the city as well, no idea what’s going on
(Perhaps my computer is just a bit weak)
