[gzdoom-g2.1.pre-1159] Multipart model issue

Bugs that have been resolved.

Moderator: Graf Zahl

Locked
User avatar
MaxED
Developer
Developer
Posts: 47
Joined: Fri Aug 03, 2012 0:06

[gzdoom-g2.1.pre-1159] Multipart model issue

Post by MaxED »

The wiki made me believe that only model 0 will be rendered in this case:

Code: Select all

Model RTCWPhone
{
	Path "models"
	Model 0 "phone1.md3"
	Skin 0 "phone.jpg"
	Model 1 "phone2.md3"
	Skin 1 "phone.jpg"
	Model 2 "phone3.md3"
	Skin 2 "phone.jpg"
	Model 3 "phone4.md3"
	Skin 3 "phone.jpg"
	
	FrameIndex SMGT A 0 0
}
In reality, all 4 models are rendered.
Attachments
modelparts_bug.pk3
(22.47 KiB) Downloaded 66 times
User avatar
MaxED
Developer
Developer
Posts: 47
Joined: Fri Aug 03, 2012 0:06

Re: [gzdoom-g2.1.pre-1159] Multipart model issue

Post by MaxED »

So, ummm... any chance of fix or an explanation of the actual logic GZDoom uses here?..
User avatar
Graf Zahl
GZDoom Developer
GZDoom Developer
Posts: 7148
Joined: Wed Jul 20, 2005 9:48
Location: Germany
Contact:

Re: [gzdoom-g2.1.pre-1159] Multipart model issue

Post by Graf Zahl »

No explanation and no fix. Sorry. Much of the model code was inherited from Skulltag so some of the logic even escapes me...
User avatar
Rachael
Developer
Developer
Posts: 3651
Joined: Sat May 13, 2006 10:30

Re: [gzdoom-g2.1.pre-1159] Multipart model issue

Post by Rachael »

In that case, the most logical thing to do is contact the person who worked with Skulltag the most during its OpenGL era - and that would be Torr Samaho.
User avatar
Graf Zahl
GZDoom Developer
GZDoom Developer
Posts: 7148
Joined: Wed Jul 20, 2005 9:48
Location: Germany
Contact:

Re: [gzdoom-g2.1.pre-1159] Multipart model issue

Post by Graf Zahl »

This was incorrectly initialized to 0 instead of -1.
But if I change this now, it'll cause an uproar because it's almost a given that some people got it wrong.
So I'm leaving it as it is. You can manually set the frame of each model to -1 and let it disappear.
Locked

Return to “Closed Bugs”