FSIC Messageboard
  Help / FAQ
  Tobruk wont be released...

Post New Topic  Post A Reply
profile | register | preferences | faq | search

UBBFriend: Email This Page to Someone! next newest topic | next oldest topic
Author Topic:   Tobruk wont be released...
Diego Lozano
Pilot
posted 01-21- 09:11 PM     Click Here to See the Profile for Diego Lozano   Click Here to Email Diego Lozano     Edit/Delete Message   Reply w/Quote
Tobruk wont be released until we find a solution for the collision problem we're having. We've looked at it, Nats looked at it and now we need some fresh ideas.

Since this terrain doubles as a ground/air terrain we just have to fix this. We wont release another incomplete terrain.

If you can help please get in touch with Rendsberger. I cant even describe the prob all that well.

IP: Logged

ArgonV
JAG
posted 01-22- 11:29 AM     Click Here to See the Profile for ArgonV   Click Here to Email ArgonV     Edit/Delete Message   Reply w/Quote
What objects/parts/pieces are not detecting object collision?

Youve tried checking the flags, polygon color, material and so on? Youve set the right properties in OPS? Youve made sure everything is defined in all the *.ppf files?

[This message has been edited by ArgonV (edited 01-22-2002).]

IP: Logged

Diego Lozano
Pilot
posted 01-23- 11:44 PM     Click Here to See the Profile for Diego Lozano   Click Here to Email Diego Lozano     Edit/Delete Message   Reply w/Quote
All I know is that one tile wont detect collision on a portion of it. The rest of the details Rends will know more about.

IP: Logged

Diego Lozano
Pilot
posted 01-24- 10:37 PM     Click Here to See the Profile for Diego Lozano   Click Here to Email Diego Lozano     Edit/Delete Message   Reply w/Quote
BUMPITY BUMP BUMP BUMP

IP: Logged

Pierre Radiateur
Pilot
posted 01-25- 02:55 AM     Click Here to See the Profile for Pierre Radiateur   Click Here to Email Pierre Radiateur     Edit/Delete Message   Reply w/Quote
IT sounds a bit radical, but have you tried replacing those tiles with freshly made ones?

It sounds as though there is a problem with the actual LOD values that is preventing collision detection. The terrain tiles themselves do not have much by way of properties.

I would start with importing a replacement 'flat' tile, see if that fixes the collision pproblem. Then, re-make and re-texture the offending tile, and import that.

Might also be worth looking closely at the LOD files for each 'problem' tile. MAke sure the LOD flags match those on the other tiles. Could be you have a rogue one!

------------------
The Pilot formerly known as W.T.G.

IP: Logged

Rendsburger
Pilot
posted 01-25- 07:32 AM     Click Here to See the Profile for Rendsburger   Click Here to Email Rendsburger     Edit/Delete Message   Reply w/Quote
Guys,
i replaced the 3dmodel of the tile several times with no luck.I used selfmade tiles or imported a working one and i got everytime the same result that a part of this 4point square didnīt detect collision.
If i look at the lod itself then i canīt find something wrong with it.
The city was made with 5 terrain tiles so look here:
-----------------------------------------------This is LOD 000 and working------------------------------
1 LODShape
1
1600000000.
4
1280.000000 -1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 1.000000000 0.000000000
1280.000000 1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 1.000000000 1.000000000
-1280.000000 1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 0.000000000 1.000000000
-1280.000000 -1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 0.000000000 0.000000000
1
0fff 2 4 0 10 0.000000000 0.000000000 1.000000000 0 1 2 3
---------------------------------------This is LOD001and working--------------------------------------
1 LODShape
1
1600000000.
4
1280.000000 -1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 1.000000000 0.000000000
1280.000000 1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 1.000000000 1.000000000
-1280.000000 1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 0.000000000 1.000000000
-1280.000000 -1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 0.000000000 0.000000000
1
0fff 2 4 0 10 0.000000000 0.000000000 1.000000000 0 1 2 3
-----------------------------------------------This is LOD002and working-------------------------------------
1 LODShape
1
1600000000.
4
1280.000000 -1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 1.000000000 0.000000000
1280.000000 1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 1.000000000 1.000000000
-1280.000000 1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 0.000000000 1.000000000
-1280.000000 -1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 0.000000000 0.000000000
1
0fff 3 4 0 10 0.000000000 0.000000000 1.000000000 0 1 2 3
........................................This is LOD003 and Corrupt!!!------------------------------------------
1 LODShape
1
1600000000.
4
1280.000000 -1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 1.000000000 0.000000000
1280.000000 1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 1.000000000 1.000000000
-1280.000000 1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 0.000000000 1.000000000
-1280.000000 -1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 0.000000000 0.000000000
1
0fff 4 4 0 10 0.000000000 0.000000000 1.000000000 0 1 2 3
--------------------------This is LOD004 and working-------------------------------------------------
1 LODShape
1
1600000000.
4
1280.000000 -1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 1.000000000 0.000000000
1280.000000 1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 1.000000000 1.000000000
-1280.000000 1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 0.000000000 1.000000000
-1280.000000 -1280.000000 0.000000000 0.000000000 0.000000000 1.000000000 0.000000000 0.000000000
1
0fff 5 4 0 10 0.000000000 0.000000000 1.000000000 0 1 2 3

---------------------------------------------------------------------------------------------------------------------
There are also no properties if you look at these tiles using OPS

Rendsburger

[This message has been edited by Rendsburger (edited 01-25-2002).]

IP: Logged

Rendsburger
Pilot
posted 01-26- 07:59 AM     Click Here to See the Profile for Rendsburger   Click Here to Email Rendsburger     Edit/Delete Message   Reply w/Quote
Guys,
this is realy something for Fox Mulder and Scully.
If i move the tile to a different location then it detects collission,mysterios or?

But i guess i have an idea how to solve the problem,report later...

Rendsburger

IP: Logged

Nat
JAG
posted 01-26- 11:06 AM     Click Here to See the Profile for Nat   Click Here to Email Nat     Edit/Delete Message   Reply w/Quote
what we're actualy talking about Rends, isn't replacing the LOD, but replacing the tile, delete the damn thing, copy one of the others and put it there instaed, all you have to do to get the right texture on it is change the obTileID, then you get around trying to fix it, and just put on in there that you know is fine, or have you tried this already?

IP: Logged

Rendsburger
Pilot
posted 01-26- 12:08 PM     Click Here to See the Profile for Rendsburger   Click Here to Email Rendsburger     Edit/Delete Message   Reply w/Quote
Nat,
yes i delete and replaced the tile a few times.
But now i found a solution based on a tip you send to me. I added an invisible tile to the terraintile.What you are seeing in game now is the corrupt one but the collision detection comes from the invisible tile

Rendsburger

IP: Logged

Pierre Radiateur
Pilot
posted 01-26- 12:10 PM     Click Here to See the Profile for Pierre Radiateur   Click Here to Email Pierre Radiateur     Edit/Delete Message   Reply w/Quote
Have I got this right ....

This is one tile from a city, and it is a simple square single polygon? Looking at the lod, it only seems to have 4 points defined.

If that is the case, and only a PORTION of the tile is not detecting collision?

If that is the case, then the tile itself isn't the problem. A single polygon will either detect or not, depending on it's properties.

I would guess that you tile is sitting IN the terrain. When I messed about with runways and stuff, I found that you got odd results if you layed a tile in the same place as a terain part. It may be that your terrain has a slope here, and the city is sitting on that slope. Part of the tile is intersecting with the terrain, causing your odd effects. IF you raise the co-ordinates of the city to lift it up a fraction, the problem should go away. Ultimately, you will need to shape the tile to match the terrain.

Of course....this may not be the problem!

IP: Logged

Rendsburger
Pilot
posted 01-26- 01:26 PM     Click Here to See the Profile for Rendsburger   Click Here to Email Rendsburger     Edit/Delete Message   Reply w/Quote
Pierre,
yes i thought that this could be the problem and i tried to lift the tile 500ft up and got the same bad result.It only works ok when i moved it on the x,y axis away from the location.
But now it it seams to work if i use the trick i described before.Now iīm only waiting to get the same positive result from a betatester before i release it.

Rendsburger

IP: Logged

Nat
JAG
posted 01-28- 12:46 PM     Click Here to See the Profile for Nat   Click Here to Email Nat     Edit/Delete Message   Reply w/Quote
Just glad you've been able to fix it Rends, at the end of the day, who cares how aslong as it works LOL

IP: Logged

All times are CT (US)

next newest topic | next oldest topic

Administrative Options: Close Topic | Archive/Move | Delete Topic
Post New Topic  Post A Reply
Hop to:

Contact Us | Fighter Squadron Information Center

(This site Copyright (c) 1999 Inertia LLC)

Powered by Infopop www.infopop.com © 2000
Ultimate Bulletin Board 5.45c