airflamesred opened this issue on Dec 15, 2008 ยท 6 posts
airflamesred posted Mon, 15 December 2008 at 12:24 PM
nruddock posted Mon, 15 December 2008 at 1:05 PM
Quote - Is the problem
a) My modelling
b) Crossroads
c) Both of the above
d) Something weird
Any ideas from you lovely people?
We can rule out a) and c) as the model looks alright when imported as COB.
The most likely problem is that Crossroads doesn't understand something in the COB file.
If there is an option to freeze/convert/bake to polygons before exporting from Metasequoia I'd try that first.
What other formats will Metasequoia export too ?
There may one that Crossroads can do a better job of converting to OBJ.
Or if you have Bryce 6, you could export the OBJ file from it, as it appears to be able to read the COB properly.
EnglishBob posted Mon, 15 December 2008 at 4:35 PM
I agree, for what it's worth - Crossroads is old, and as far as I know isn't being developed any more. The link I had for it has gone dead, anyway. Bear in mind also that you're dealing with Metasequoia's idea of what a COB file should be, so the opportunities for error are multiplied.
My go-to app for COB - OBJ conversion is usually Compose, but that's old and unsupported too so you may well be faced with a similar problem.
Another thought: trueSpace 7.6 is free. If THAT can't make sense of a COB file, then maybe nothing can...
airflamesred posted Tue, 16 December 2008 at 5:22 AM
I'm gonna spend me money on the shareware metasequoia with obj export and pray.
thanks to you both
ShawnDriscoll posted Thu, 18 December 2008 at 2:36 AM
n-gons in there that Bryce doesn't like?
airflamesred posted Thu, 18 December 2008 at 4:50 PM
