 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
That would explain everything, the correct fix (deleting the org stuff from the bounding box, not adding it to the vertices) is in place and the robot now hits a minimum of -24, which I assume was the intention. Here's a link to the new 0.4 download, once I hear a thumbs up from Qmaster I'll update the blog.
http://www.quaketastic.com/files/tools/windows/misc/md3tomdl-0.4.zip I'm not getting any different results? Maybe you uploaded the wrong exe or something? I deleted all md3tomdl's on my end and redownloaded again, but it still doubles away from the origin, and there's still the wierd crash without a skinfile line (not that it matters much, I have skinned it now, but it's nice to have for robustness). I checked the source code that you provided and it looks like you fixed it for both cases, but the actual exe doesn't seem to have the changes?
Dunno what's up. I'm going to the source. I think Preach's program works fine enough for his workflow...it's blender's exporter that doesnt provide a similar md3 file. From what I've read, Pop'n'Fresh's md3 exporter for gmax determines the bounding box for each frame. I found the source code for it here: http://forums.duke4.net/topic/1065-md3-exporter-for-3ds-max-2010-x86-and-x64/ I'll check it out when I get a chance and compare it with the katsbits exporter for blender. I might have to modify the blender exporter to match the gmax one. Translating from c++ to python here so wish me luck.
I think the uploads might havegot mixed up, yes, try this one.
http://www.quaketastic.com/files/tools/windows/misc/md3tomdl-0.4.zip So what's the easiest path for someone who wants to make a static prop to get it built and into Quake in MDL format? I saw, to my surprise, that Milkshape is still selling full licenses (wtf?) and I'd like to stay legit if at all possible.
http://quakeforge.net/ has a Blender plugin, taniwha is super nice and helpful in case it should not work.
If you have Maya at home I've written some python doodads. They go through a hacked modelgen.exe atm but I'm planning on merging it with Preach's pymdl so it all works within Maya.
The blender route seems the most sane at the moment
Of course I'm totally biased toward blender but I'm biased for a reason, it's awesome. I was considering looking at creating a blender addon using Preach's qmdl python package since all of blender's addon's are scripted in python, but it currently has an md3 exporter which works nicely with Preach's md3tomdl, especially for static props (don't forget to unwrap them before using blender's md3 exporter! got my goat several times for that one)
Exporting directly to it just feels so... liberating. No annoying conversion pipelines in between, no messing with qME to import a skin, etc.
There's a MD3 script too, but it has a horrible 'auto-scale' which makes my models too big by default having to input the manual scale to 1.00001 every time to turn that off. There's also a nice ASE exporter script for q3map2 use, however it shits the UV on certain turned edges. Trial and error for that You know I started trying it and I'm hooked on direct export to mdl. The only thing I haven't figured out is how to get it to export in a different palette. No matter though since darkplaces has a skin override feature: mymodel.mdl_skin0.pcx
I'm hoping to avoid the time to trial and error....what axis should weapon view models look down?
And how should the view model be positioned relative to the origin? For anyone who's using the fbxtomdl converter to get their model fix on, there's a new version out at:
http://tomeofpreach.wordpress.com/qmdl/fbxtomdl/ Like the past few updates to md3tomdl, the changes are minor refinements rather than new features. The main bug this one nails is inaccuracy when converting skins - the UV coordinates are now always snapped to the centre of the pixel they lie within. The other changes relate to the latest version of the fbx library - the code has been made compatible and the pre-compiled version has been upgraded to include it. Does this
Damn it. I'm terrible at this stuff. I think I installed stuff correctly but I get this error when running it:
https://dl.dropboxusercontent.com/u/161473/Misc/Bugs/FBXToMDL.jpg Here's the FBX file but I don't think it's related https://dl.dropboxusercontent.com/u/161473/Misc/Bugs/Q_Plaque.fbx Annnnd it's because I didn't have a skin file in the folder. Never mind, I have an output.mdl created! Continuing to play...
Sorry for spam. It's actually a useful touch of feedback, not just to hear that someone's making use of it, but it might actually be an indication that something needs fixing. There's meant to be code that handles the case when no skin file is present by adding a dummy skin, but it looks like it's not working. Possibly the bug is isolated to the pre-built version, and maybe it's the warning message that's triggering things. I'll test a bit and see if I can fix that...
If you ever need a kidney or something, preach, let me know. Damn...
https://dl.dropboxusercontent.com/u/161473/SeptQuake/CustomModels.jpg I never thought it would be this easy. I was procrastinating because the thought of Blender plugins and such was turning me off. But this... THIS... So I'm messing around with model skins and I'll be damned if I can figure this out
I can't get the right colors to show up inside of Quake. I don't have a custom palette in any of my WAD files https://dl.dropboxusercontent.com/u/161473/SeptQuake/palette.jpg I either get black models or the colors seem shifted off by one row Is Photoshop not the right tool for painting Quake skins? It has to work, right? I'm exporting an 8-bit, indexed PCX file...
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |