Welcome to Fractal Forums

Fractal Software => Bug Reporting => Topic started by: KBeezie on October 15, 2013, 02:21:37 AM




Title: bad lightmap/texture path in windows (command line, client mode)
Post by: KBeezie on October 15, 2013, 02:21:37 AM
Not 100% sure if I can call this a bug because I don't know entirely if it's been fixed in 1.17.2.

I'm using OSX Lion (10.7) as a server with 1.16 (because it won't connect as a client to the windows version of 1.16, only as a server, it gets a rejected message when trying to connect to a windows server even with firewall off).

So I got one OSX machine running as a server in GUI Mode (guess no nogui for server?), and 3 windows machines also running 1.16 (otherwise they couldn't connect due to version mismatch).

The problem is if I use the OSX GUI and try to render something with Ambient Occlusion, I get rows of the image not matching the right shading and such and I determined that this was because the windows clients were trying to pull /usr/share/mandelbulber/textures/lightmap.jpg as specified by the server which doesn't exist on windows clients, and the .default in /Users/[Username]/mandelbulber/.default keeps being reset to the "C:\Program Files (x86)..." path whenever the client starts back up.

So far the only way I could get both an OSX Server and Windows clients to behave properly and all load the light map was to copy the textures folder to the default home dir (ie: /Users/[username]/.mandelbulber on OSX, C:\Users\[Username]\mandelbulber on Windows), and then lock the C:\Users\[Username]\mandelbulber\.defaults to read-only so it doesn't revert from the "textures\..." path, which I also set on the OSX side.

Once I did that all the clients were rendering the proper light mapping/AO because they were looking for the file in their relative texture directory instead of absolute paths which won't work on two different kinds of systems. (And for some reason mandelbulber on windows hates paths with spaces in them such as "Program Files (x86)" seems to consider them not found).



Title: Re: bad lightmap/texture path in windows (command line, client mode)
Post by: KBeezie on October 15, 2013, 02:23:03 AM
Also the 3 windows machines are Windows 7 ultimate (x64), Windows 8 Pro (x64) and Windows 7 Home Pro (x64). I'm running 32-bit version of 1.6 on both platforms.

(though I wish I could use one of the windows machines as the server, as the OSX version has a habit of freezing up at 99.722% and has to be forced closed when used in GUI mode there).