Ziemanskye on 5/11/2005 at 21:44

---

No, I wasn't using the generator - I was trying to do it by hand to see how it worked.

Too used to the MCDC*_* collisions of UT2k3 I guess.

And I've got it in the editor now, and it doesn't seem to want to cast shadows. Thankfully I didn't want it to, since it's a glorified lighting effect, but if anyone else tries to use it, that could be a problem.

*sigh* You'd think this'd be easy.

Though the collision thing might have been me not setting up the dummy objects right - the old post I read describing how to do this said the ones from the script had a user defined property with names COLL and COHI before it hit the actual collision meshes, which I didn't have (having never had to add user defined properties before, so not know how)

Edit:
Okay, insert healthy does of me being a moron. Have to have camera inside the level to see shadows. The points don't cast shadows, but I already knew they wouldn't (because they aren't closed meshes)

Edit 2:
Incase anyone wants to try again, I've closed the holes of the spikes (so they'd cast shadows), changed some of the UVs (cause one face was inside out, and the bevelled sides didn't work as well as I'd hoped when in game), renamed and moved the dummy objects a bit (and added the User Defined names, so hopefully they'd pick up right), and capitalised the collison models (because it looks important in the collision maker script - it doesn't run but I could read the maxscript code)

(http://img127.imageshack.us/my.php?image=collhierachynew8ee.jpg) http://img127.imageshack.us/img127/1383/collhierachynew8ee.th.jpg
and it's in *.max, *.3ds, *.ase, and *.obj here
(http://rapidshare.de/files/7242914/Collector.zip.html)

ascottk on 11/11/2005 at 19:00

---

Yeah the texturing is pretty strange. It would actually be cool for a cell shader mod though.

I had to redo the collision meshes because max 5.1 exports the collision meshes as regular meshes. I don't know why but it doesn't really matter beause it's easy to fix.

Here's they are, BTW:
(http://rapidshare.de/files/7493601/STiFU_Meshes.rar.html)

Ziemanskye on 11/11/2005 at 22:00

---

Hey ascottk, I had a thought about why the collision meshes don't seem to want to work - you said it's the *.ase files that you're working with right (because the *.max are version specific, and the *.3ds mangle the names)?

I read one in notepad, and it throws away the User Defined COLL and COHI names in the dummy objects, so maybe that's where it's going wrong - the script isn't finding what it thinks it needs to recognise the objects...

It's just a thought but if you could spare the time to check by loading one of the uncompiled things and adding those properties yourself it'd be cool - ruling out options is good, and it means we can get some more info for how to set things up incase we ever get an arbitrary *.tim compiler.

Ziemanskye on 11/11/2005 at 22:28

---

Well, to further complicate things, could you try that with the collision objects names copied into User Defined properties?

Part of the idea here is to work out how to do collisions entirely manually (as in not run the collsion maker script at all, just export to *.tim and hopefully carry the manually setup collisions, rather than turn them into seperate objects).

And/or could you post me a simple object that does work with the script, so I can compare notes?

Ziemanskye on 12/11/2005 at 11:21

---

Well, if you don't want to that's cool, you've already been a great help to us.

What I was meaning though (sorry, tend to assume people know more about the software than I do), is to select the collision objects, right-click and select properties, then under the User Defined tab copy/paste the HKConvex_* name into it to see if it recognises it there, though I don't think that the odds aren't very good.

For the record though - I didn't finish t2x either - I think I skipped some missions because I'm just not interested in the undead, or the weird non-human-ness of the pagans.
I don't have doom 3 yet, so I definately haven't finished that.