Hi Boeufmironton,
This has been buggering mappers for ages and I salute your efforts to sort it out.
Just one thing, next time you want to rework some official material please get in touch with me first, this could avoid unnecessary duplicate work.
I'll explain...
You haven't been around for a while so they are obviously a few bits and pieces that have evolved/moved/changed within the game that you are not especially aware of (like you ladders added to package for example).
First off note that for various reasons we have now moved on to .md3 and that in next version all mapmodels are reworked and converted to that format, I suggest you start using SVN so that you can stay up to date with development.
(EDIT: RK posted while I was replying ;) )
So, right now in SVN these fences models are already converted to .md3, but still remains the glitch you mentioned and the pretty much ugly z-fighting...
![[Image: rWyJYH3.jpg]](http://i.imgur.com/rWyJYH3.jpg)
Some time ago Bukz asked me if you could have look at that z-fighting issue and eventually fix it... To get rid of it the main idea was to switch from the actual 2D flat plane using .png image to a proper 3D grid using .jpeg, whilst doing so I also fixed that blending problem...
![[Image: OJpvRcC.jpg]](http://i.imgur.com/OJpvRcC.jpg)
Unfortunately the problem I was now facing is that with a full 3D model the polycount is unacceptable... V=402, T=592 and even more for the models with doors (keep in mind that they are often several of these models in a small area). After a few other tests I figured out that another way around it was to go for what you exactly just did... 2 planes close to each other and with .jpeg skin.
Anyhow, although at the end of the day the result is still somewhat arguable with polycount at V=423, T=264 (just the fence) they are the best option so far and since I haven't yet reworked the models that way myself I see no objection at all at adopting your models for next version.
I will however discuss the case with other devs and I'll keep you posted about the outcome.
PS: Be careful with MilkShape, it has the bad habit of automatically set frames count to 30, remove them before exporting, your model should only be 10Kb not 320Kb ;)
RePS: I took the liberty of optimizing the skin.jpg file... 200Kb > 70Kb (no visual alteration whatsoever ;) )
![[Image: w7iM2xG.jpg]](http://i.imgur.com/w7iM2xG.jpg)
This has been buggering mappers for ages and I salute your efforts to sort it out.
Just one thing, next time you want to rework some official material please get in touch with me first, this could avoid unnecessary duplicate work.
I'll explain...
You haven't been around for a while so they are obviously a few bits and pieces that have evolved/moved/changed within the game that you are not especially aware of (like you ladders added to package for example).
First off note that for various reasons we have now moved on to .md3 and that in next version all mapmodels are reworked and converted to that format, I suggest you start using SVN so that you can stay up to date with development.
(EDIT: RK posted while I was replying ;) )
So, right now in SVN these fences models are already converted to .md3, but still remains the glitch you mentioned and the pretty much ugly z-fighting...
Some time ago Bukz asked me if you could have look at that z-fighting issue and eventually fix it... To get rid of it the main idea was to switch from the actual 2D flat plane using .png image to a proper 3D grid using .jpeg, whilst doing so I also fixed that blending problem...
Unfortunately the problem I was now facing is that with a full 3D model the polycount is unacceptable... V=402, T=592 and even more for the models with doors (keep in mind that they are often several of these models in a small area). After a few other tests I figured out that another way around it was to go for what you exactly just did... 2 planes close to each other and with .jpeg skin.
Anyhow, although at the end of the day the result is still somewhat arguable with polycount at V=423, T=264 (just the fence) they are the best option so far and since I haven't yet reworked the models that way myself I see no objection at all at adopting your models for next version.
I will however discuss the case with other devs and I'll keep you posted about the outcome.
PS: Be careful with MilkShape, it has the bad habit of automatically set frames count to 30, remove them before exporting, your model should only be 10Kb not 320Kb ;)
RePS: I took the liberty of optimizing the skin.jpg file... 200Kb > 70Kb (no visual alteration whatsoever ;) )