[Ben]

QUOTE (Craig Kostelecky @ Apr 21 2006, 04:14)

I do #35 now each time I rebuild the image.

So that'll be right for the next update?

[spaceeinstein]

#36 is some kind of corruption in the DFF file. If you replace that building with the original GTA3 building, the problem would be fixed but the building will have only one-sided textures.

[Ben]

Choofy should be aware of these model loading problems - they're always in the bugs list, and there's a few in his model fixes topic.

The problem, however, is that he's not active much anymore. Craig's working on renewing his interest though, I think .

Those aren't real major bugs anyhow - they'll get fixed eventually .

About #37 - do you think you can fix it through your occlusions? Or does it need a complete model revamp?

Good work at detailing those bugs anyhow - thanks .

[spaceeinstein]

In my game, #37's problem was fixed. I was not able to see through the building in my game. It could've been fixed already and that was just an old bug.

[Ben]

True. I haven't tested it yet - it was just in the bugs topic, so I slapped it on the list to be sure . Cheers.

[nitzkit]

You know, I noticed you didn't do an update on the LCgeneric.col
Why is that? there are still some stuff wrong with the cols

This post has been edited by nitzkit on Saturday, Jun 10 2006, 06:10

[Ryan_]

Ok,I know, this is one hell of a bump. But, I was just looking at the checklist for LC final, and in the collision section i see three things that need fixing.
4 and 5 are easy fixes, but I dont understand 7.
Hows does this have to do with the building cols?
So, im gonna fix these cols. I'm also gonna fly around some and see if I cant find more issues to add to the list, I am sure there is some.
So, pls let me now if these have been addressed already, and how 7 fits in this section...

[Craig Kostelecky]

In GTA3 when the car was picked up with the crusher, the collision for that car went away (meaning you could walk right through it and the player would not attempt to enter the car if you pushed the Triangle button (PS2 controls). It's a collision issue, but not an issue with the col files. And as far as I'm concerned, it's not a big issue at all.

[Ben]

Yeah, not a real big issue, but something we still need to tackle at some point.

Is there some opcode that can be run through the SCM to remove a car's collision data once it has been recognised by the crusher? Or some other solution?

@Ryan_ - Good to see you're still around. Any work you could do on the COLs would be much appreciated .

[Ryan_]

I actually think it's kinda better the way it is. If your gonna get in the car when the crusher is picking it up, you deserve to die LOL

edit: ok, for issue 4, there is missing polygons, but its not on the bridge. the ground peice is missing between the building and the bridge. so that is a model issue.
issue 5, it seems the colfile for the building is either a little high, or maybe just incomplete on the bottom. this model is skyscrapenew. who do i send the repaired file when im done with it?


This post has been edited by Ryan_ on Sunday, Apr 1 2007, 02:57

[Ben]

I'll fix that up on the checklist for you . Thanks.

And send the stuff off to Craig please as he's coordinating the update packages .

[Ryan_]

OK, so I have the colfile, and ofcourse the invisable walls. these invisable walls seem to be large, but i can see them in anything. Not GTA, not max, not sketchup and not even CE2. CE2 optimize doesnt help me either. But I have a few more things to try.

edit: is there some sort of jetpack mod or something? or something like sobiets airbrake?

[space_einstein]

LithJoe's trainer?

[GTAThomas]

Holy crap! It's Ryan_. Haven't seen you since MTA...but that's another story.

I wonder if these are all the collision bugs...I remember Konstantinos and I finding quite a few a long time ago (though mostly him). I think I'm going to double check now that I got my LC up to date a few days ago.

[Ryan_]

Ok, I think I found a way to deal with the invisable walls. I broke the model down to several very simple boxes. Each box is its own group, all groups combined to make the component. I think the walls are gone with this method.
Thomas! Hey bro looooooooooooong time no see!
I havent tested much in LC, but I did find 1 thing already, so I am sure there are other col issues.

edit:
Ok, I just wanted to say, since skyscrapenew (the building I just fixed) is in the comSE colfile, I will check the buildings in this file first. I thought I would mention it since a few col makers posted, and we dont want to be doing double work.

edit 2: Ok, I just got a reply pm from Craig, telling me to send the files to Ben. LOL
So, I dont know what to do with the files.

This post has been edited by Ryan_ on Thursday, Apr 5 2007, 20:21

[Ryan_]

OMG, It's almost a one year bump.... hehe
Anyways, I was thinking about LC the other day
and set myself up again with the software.
I know for sure that there are still several if not
many collision issues still to be addressed, and I
decided to have a look through them all again.
However, this time I am not looking for ways to
cut corners, or to absoulutly minimalize poly count.
This time around I am going to make true and
proper collision files. As well, I will be able to
surface the files too.
If there is no interest in these files please let me
know, I dont want to waste mine or anyone else's
time with something they don't want.

[SteaVor]

I'm really glad to see that you're back! Any contribution would still be much appreciated, of course.
As you can see there are just 4 major COL issues remaining, so you can concentrate on optimizing the collisions and surface data..

[Ryan_]

Boo!
Wow, it sure has been a while now...
I was thinking of playing through GTA 3 the other day and though about playing it with the LC mod instead.
Any idea if there are any major collision defects still to be corrected?
Cant wait to see all the changes since I last played this mod.
Hopefully I can find something that I can still do to help out. It's been ages since I modded any GTA files.
It would be nice to see LC Final actually released in the future, but I am sure there is ALWAYS something someone can do to make it even better .
Glad to see some names I recognize returned here aswell.
Hope to see you all more often.
Hopefully I wont get sidetracked and will post here with any collision defects I find (I am sure there must be atleast a few).

[Craig Kostelecky]

The mod is currently at a stand-still as we await ModelingMan's latest update. I was working closely with him back in May-June, but had to move to a new house and had leave my desktop computer behind. I'm now back in the house I lived in from 2000-2007 so I do have computer access again. However I'm raising two boys that are under 2 years old by myself right now. So I'm not doing much more than that. Luckily everything that I am capable of doing has already been done. MM just needs to tweak the launcher files a bit more before we release the final version. I have not heard anything from ModelingMan since I moved in June, but expect that he'll pop back in when his time allows him to.

I'm not sure what the current state of the collision data is. You can download the Beta 3.1 package and that will show you what's missing. The DeLorean has received a bit of an upgrade so it will be more enjoyable to test it out.

[silver007]

QUOTE (Ben @ Mar 28 2006, 18:16)

Bug 38. See-through fire escape stairs IMAGE

So I've found out how to fix any culling issues such as the one above:
Before / After

Problem isn't with the model's triangles, its the Material Index. When the materials using alpha's are higher than the rest of the textures (as was the case with the 2 models that make up that section of buildings) They cull the rest of the model. By reordering the materials so that the ones using transparency are at the bottom, it fixes that issue.
However, it obviously requires opening up the model in an editor and re-exporting it. I'm using 3DS max and therefore the new exported models may have problems such as losing lighting data, or other things I am not aware of, since as far as I am aware using Kam's scripts to import/export a model isn't truly a 1 to 1 process.

If this fixes the issue to our satisfaction, then point me in the direction of any other model that needs fixing, it only takes a minute to do.