Has anyone been playing with a way of getting float data out of WM into a 3d app? I’m converting .r32 into .hdr for use in 3DStudio but hitting problems with my conversion pipeline.
Are there any plans for more file output formats?
I have some experience dealling with TGA… But TGAs with WM will not give you the range you what…
What problems are you having? Is it on the .r32 end or the .hdr end? I’m not familliar with .hdr format. My .r32 knowledge is not famous either, but it’s better
You may also consider using MaxScript to load stuff into 3DStudio (I don’t remember if MaxScript can read text or binary files).
Btw, WM is HUGE!
Well.. I think WM is very small (~2MB) compared to the file size of heightfields it can write ;)
I have no trouble with raw data but for max I need to convert it into a more common floating point format like HDR (high dynamic range image) or open EXR (another floating point format). Somewhere in between the conversion I seem to be clamping the data and end up with terracing in my displacement mapped landscape in max (Vray). I guess I was hoping for some sort of alternative way of extracting floating point data from WM than raw32.
To get that info out directly, without using r32, I don’t know… (using .ter format could be one way) Though, you might be able to use leveler to convert to something else… I don’t know very well what leveler can do, but it might be worth exploring.
Doesn’t r32 have a header stating the ranges of values? Or aren’t they between 0 and 1?
Well I fear from now on I’m talking blindfolded in the dark
Better wait for someone with more knowledge on that to answer…
I was waiting for Stephen to ask him that I know using the PDK, it’s possible to do our own exporter, but I don’t think it will be possible to include it in the File Output device. It has to be a new device… (I think)
Well you could make a ‘new file output’ device I would think.
I’m having a similar issue with Maya, but I think I have it solved. I export from Leveller as a 24 bit TGA, then I have a custom Maya node to sum R65536 + G 256 + G … playing with, but it’s working better.
You really need higher range outputs for terrain to look good.
Making a ‘pov ray’ 16 bit out or a 24 bit out would be easier than going through Leveller of course. Maybe I’ll work on it but don’t hold your breath.
My big issue now is roads … a road plugin would have to come first.
There are indeed some plans for more file output formats, some in the upcoming 1.1 release and others later. But for very specific export needs writing a custom exporter plugin might not be a bad idea. There are some specific details for writing an exporter that should be addressed; post in the PDK subforum if you’re interested in this route.
Edit: Wow, that was convenient. As soon as I finished writing my original message I though I’d read up on the .hdr format to see if i could write some sort of plug-in.
So I open HDR Shop to get started and guess what? Right their is a import RAW funciton. Works with RAW-FP32 just fine.
However, I too am having some issues with information being ‘clipped’.
I’ll keep at it and keep you guys posted. [/url]
ps…about clipping values and terracing on import to Max, that’s a Photoshop color conversion/color management issue. Turn off color management in ps and try it again…