12 replies to this topic

[L0N3 W0LF]

A Little problem i have with Sections in a particular unit... This vehicle is called "Scorpion"... its the anti-air vehicle for the Red Army... I made a specific HVA file as it uses multiple sections... It looks perfect when viewed in Voxel Viewer and HVA Builder...but the sections appear wrong places in-game.. i have attached 2 previews.. anyone familier with this phenominom? ... help me out...

EDIT: the two pieces at the Left and Top of the vehicle are the problems.. the turret works fine... and ignor the Apocalypse Tanks... they just got in the way...

Attached Thumbnails

• 
• 

Edited by L0N3 W0LF, 04 December 2007 - 05:12 PM.

[Mig Eater]

Most likely a header problem, don’t believe everything the voxel & HVA programs show you BTW. Why are you trying to join the grizzly & rhino turrets together anyway, you’ll most likely get over lapping problems between the two of them & the missile pods. It’s best to make one whole voxel instead of randomly sticking a few together.

[Blade]

Agreed, HVA files are for making sections move relative to each other, not to glue together a load or random parts into a solid whole. Thats what XCC mixers convert to text function is for and is partly how me and Cannis made some of the IFV turrets and how Sleipnir made some of his voxels back when RA2 was fairly new.

[L0N3 W0LF]

I actually don't know how to do that... But i really wanted to.. is there any tutorial on how to do that.. I mean, the xcc txt convert thing..

[Mig Eater]

Convert two vxl files to txt with XCC, the copy & past them into one txt file & convert back to vxl. That’s pretty much it, it’s not hard to get the hang of after a few tries.

[Blade]

The hardest part really is preparing the voxels before the merge. It helps to set the sizes to the dimensions you expect the final voxel to be and to move the bits you want to glue together to where they will be in the final voxel as well. Then when you merge them, the result is what you expected it to look like. You will need to edit the bounds once you've merged them as XCC doesn't save that information into the text files. To be honest I think its quite an arcane technique, I've not seen many voxels that appear to be made using it.

[Mig Eater]

Actually I use it a lot, comes in handy when doing batch conversions.

[SSTG]

Might have to remember this trying to make a IFV prism turret

[L0N3 W0LF]

Many thank... That is gonna lighten up things for my quite a lot...
but i have a ready made a new "scorpion" from scratch... looks a little better now... but i'll compare both outcomes... and implement thre one that looks better... so wait till my birthday to see a demo of World War III...

[TX1138]

The text2voxel conversion technique doesn't handle normals well. Which is a pity because that was one of the things that I was trying to get right.

[Blade]

Yes it does, unless you try and mix voxels that have different normal sets applied to them. For example a TS voxel merged with most of the RA2 ones will look screwed up. However if you use the auto-normaliser to apply RA2 normals to a TS voxel before trying a merge it will look fine.

[L0N3 W0LF]

ya.. i noticed that

[Mig Eater]

Not really that important but when you use txt2vxl it also removes the voxels internal pal too. The game & most editors use external pal files so it doesn’t really mater, a few will show the vxl in a messed up black & white tho.