No way to tell obj where to look for materials

Is there something that doesn't work right in the latest GZDoom? Post about it here.

Moderator: Developers

Forum rules
Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.

If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.

Re: No way to tell obj where to look for materials

Postby phantombeta » Fri Nov 02, 2018 11:56 am

Major Cooke wrote:But deprecating the skin property... How else are we supposed to provide the textures for it? How do you put them in and have them export via blender directly into the model then? I for one have seen NO signs of being able to ever do this. Please do tell me how! I'd love being able to avoid needing to export the skin as well.

Second, if you deprecate the skin property, I don't see how we'll be able to apply materials like specular, normals, and bright maps.

Nash has explained how to do this before, both here and on the ZDoom Discord server.
User avatar
phantombeta
In the meadow of sinful thoughts, every flower's a perfect one
 
Joined: 02 May 2013
Location: The United Soviet Socialist Dictatorship of Hueland
Discord: phantombeta#2461
Twitch ID: phantombeta_

Re: No way to tell obj where to look for materials

Postby Major Cooke » Fri Nov 02, 2018 11:57 am

dpJudas: Being able to skip the TEXTURES definition would be appreciated. How about a "Diffuse" property where you can point to the texture file's location?

Phantom: Sweet! I'll check it out.
User avatar
Major Cooke
The road to Hell is paved in the carrion she leaves behind.
 
Joined: 28 Jan 2007
Discord: Major Cooke#0846

Re: No way to tell obj where to look for materials

Postby Major Cooke » Fri Nov 02, 2018 12:07 pm

Okay, I took a look at it, but the big question is: can it support multiple materials being used? Or do I have to bake and unwrap it?
Because that's the problem I'm facing personally which makes mtl reading far more favorable for things like this. If I scale down the UVs, the textures grow far too large and making different resolutions of textures doesn't help one bit.
Last edited by Major Cooke on Fri Nov 02, 2018 12:12 pm, edited 1 time in total.
User avatar
Major Cooke
The road to Hell is paved in the carrion she leaves behind.
 
Joined: 28 Jan 2007
Discord: Major Cooke#0846

Re: No way to tell obj where to look for materials

Postby dpJudas » Fri Nov 02, 2018 12:12 pm

Major Cooke wrote:dpJudas: Being able to skip the TEXTURES definition would be appreciated. How about a "Diffuse" property where you can point to the texture file's location?

What I'm saying here is that trying to automatically map the model format's material definitions to engine materials is often a bad idea as the data sets do not fully overlap. Even when they do, there's often problems because paths may not match, one tool might interpret it differently than the other. Subtle stuff like some properties will work, some won't. It is a can of worms.

For those reasons, I'm recommending not trying to support .mtl files directly - or at least only support for pulling out a base texture name for you. I'm not the maintainer of the obj feature, so I'm just voicing my opinion here.
dpJudas
 
 
 
Joined: 28 May 2016

Re: No way to tell obj where to look for materials

Postby Graf Zahl » Fri Nov 02, 2018 12:23 pm

I think it should work like all other formats:

Use whatever is present in the model if no skin is set, and use a skin if one is set. This necessitates removing the error message, though.
User avatar
Graf Zahl
Lead GZDoom Developer
 
Joined: 19 Jul 2003
Location: Germany

Previous

Return to Bugs

Who is online

Users browsing this forum: No registered users and 2 guests