it's no problem Ernegien, your work on this is epic, and if anyone has the knowledge and experience to help, it would definitely be him I just sent him a Forza Studio created .obj file to assess as per his request (Mazda Furai_lod0), I figured that would be the best example because of it's outrageou...

do you read and reconstruct the polys by quad? or by tri? ..as I was wondering why the mesh has the same number of both, and why it deforms into a triangular mess when converting it to editable poly - it's frustrating that any type of editing to the mesh results in unrecoverable visible flaws (eg: c...

minime891 wrote:And also the rims dont seem to map the textures.

the rims included in the vehicle_lod0 meshes are mapped to the wheel/wheel_lol0 textures found in the wheel file specific to that vehicle

↑ I would guess it's something to do with how these kats are reading/re-encoding the mesh.. there's something definitely off, because the 360 Shift DLC meshes Oleg's imports get phuckd off to and do odd things while editing them, not to mention entire parts completely disappear if you export the mes...

edit- ↑ thanks Ernegien- I still get the UE error when attempting to run the executable tho ..but the older executable uploaded by Sommergemuese works :/ edit number four thousand eight hundred fifty three got it workn, it was pulln from my net.framework 4, so I installed VB2008 and reDL'd 3.5.10 an...

*Ernegien reaches thru the monitor and slaps Kot* lol- thx man, if it was a snake I'd be dead o.O and I tested on xna 3.5 and got a "Mixed mode assembly is built against version'v2.0.507272' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information"...

can someone please compile 5.3.10? ..I only have Visual C# atm

and which xna version do I need? 2? ..3? ..3.1, 3.5, 4?

can someone please answer Smoke's question about getting the mesh into Zm please.. and please address the issue that I raised about all of the verts being broken, because unless you're doing a straight conversion (no scratch work, no working doors, ect.), the broken vertices caused by F3RET are rend...

idk if anyone else has noticed (as I have yet to see anyone mention it), and I'm unsure to which process is causing it.. but every single vertex on these models are broken - which is easily the cause for all the bad exports, chewed up meshes and misinterpreted smoothing I've seen associated with the...