3D Cities for Falcon…
-
@arty here´s the Count. Not all is perfect and editing kimpo is a nightmare that KC APARTMENT is fubared every time you delete one on LE Gives an error… So it was a labor of patience deleting those buildings. Molni this is my my standart Kimpo and with this process I can substitute it ALL in one hour or less. Instead of having a objective FULL of crap I only have one. Yes a different approach is needed if we don´t just want to nuke the city because this way it will be destroyed in one block. But working together with arty we will find a way to have a middle term. But to my conclusion to fulfill this objective will be hard because as i think We can´t had new features just edit the existing ones. Am I correct? As always I welcome humbly every help I may have. Thanks guys.
Objective 2070 before - 175 features….
After editing 1 Feature.
-
Adding new features is no problem at all
-
-
-
so…i we want 3d cities on bms we have to lose our fps… :P:(:( Nevertheless it looks really great!!!:)
-
Well I believe u could brake it down to 3 - 4 segments thus 3 to 4 features in the objective…
Man looks really great… hey where is that ground photo?
@Eleni… for now yes.
Let’s hope Code Developers will find a way to make this better… I posted some suggestions… I also would love some feedback so we could set our standards as we progress on this project.
Bmartins and I are on the talks… Maybe soon we will have something to announce. There are lot’s and lot’s of testings and learning taking place under the hood…
@Bmartins I believe we must set the Deagg values to those objectives as low as 1nm and test them to see how it goes for fps… yeap unrealistic but cities ain’t war targets… For the rest of them sure they will be default values…
-
so…i we want 3d cities on bms we have to lose our fps… :P:(:( Nevertheless it looks really great!!!:)
What about texuring? If they have maybe cost more FPS. IMHO increasing the detail level of cities of good, but maybe is not wise cover the whole textured tile if the FPS cost is too high…
What dou you think about tile based terrain improvement? Which is the easier and more flexible?
-
I got a few questions on this large cities.
How is the hitbox handled?
Are these buildings destructible?
How will AI (ground) handle that? Can they drive through it?
Is the size of the buildings in these Kimpo images correct? To me they look a bit small compared to the surrounding environment. -
I got a few questions on this large cities.
How is the hitbox handled?
Are these buildings destructible?
How will AI (ground) handle that? Can they drive through it?
Is the size of the buildings in these Kimpo images correct? To me they look a bit small compared to the surrounding environment.Hitbox not handled yet. Someone has to tell us how is that set…
I see x y z values and radius… but what do they represent and how we set them?Found this in Frugals:
@Topper:Editing hitboxes:
1. Backup your \terrdata\korea\objects folder. Do it!
2. Get and install F4browse:
http://www.simmersworld.com/default.php3?page=Miscgoods3. Once this is properly installed, open the falcon4.fed file.
4. Under the Vehicles category, double click the Mig 29A.
5. Now under the “related vehicles” on the top right, double click the Mig 29A that has the CT ID of 1848.
6. Now under the “Graphic” heading double click “Normal”.
You are there! The section labeled “Bounding Box” is the hitbox. X is the length, Y is the width, Z is the height. Record these values. For fun, change them to X: -50,50; Y:-50,50 Z:-50,50. This will make the hitbox a 100 foot cube that anybody can hit.
7. Click OK, Update, Update and close F4 browse.
8. Launch F4 SP3 and choose training mission 15. This happens to have the Mig 29A. Refrain from missiles and use the gun.
9. When you tire of this change the box to the pre-SP3 size and try it: X:-22.5;20 Y:-9.5,9.5 Z:-3.3,3.3
but why negative values?
No Sphynx I told u earlier too the towns will be splited to some sections thus bombing one will destroy the whole section.
If every building is one object (we want that also) than the FPS will go to negative values… :lol: So here we try the compromise and have a real size and number of buildings city in some objects… meaning maybe 500 or more buildings as one object… For now we have a limitation of 100.000 poly’s from LE… so whatever that makes… -
I dont know exactly how Falcon handles it, but in general game programming techniques you either use a boundingbox or boundingsphere to do collision testing (hitbox vs radius in falcon I guess).
The negative values come from the object space. A object has its own space with the origin at coordinate 0;0. Normally this is somewhere in the middle of your object or at its CG. Vertices extend in the positive and negative X,Y,Z directions. After that the object is transformed to world space and its position is relative to its origin.To determine the hitbox you just check the vertices in LE and take the outmost X,Y,Z values and enter them in the parent record hitbox.
-
I dont know exactly how Falcon handles it, but in general game programming techniques you either use a boundingbox or boundingsphere to do collision testing (hitbox vs radius in falcon I guess).
The negative values come from the object space. A object has its own space with the origin at coordinate 0;0. Normally this is somewhere in the middle of your object or at its CG. Vertices extend in the positive and negative X,Y,Z directions. After that the object is transformed to world space and its position is relative to its origin.To determine the hitbox you just check the vertices in LE and take the outmost X,Y,Z values and enter them in the parent record hitbox.
When I hear LE something goes on in my spine… Anyway to do this with values from 3ds? I believe if I have the measures from 3ds like 3000 units x and 5000units y and 200 units z than x=1500 y=2500 and z=100 meaning the half where zero point should be… meaning for x 1500 before zero point and 1500 after zero point… the same with the others… right? To be more exact Xmax=1500 Xmin=-1500 Ymax=2500 Ymin=-2500 Zmax=100 Zmin=-100
On the Z… where the ground level is??? at -100?hmmm
Now the problem is In 3ds I use meters in LE they must be feet… so LOL
-
your correct, but you have to take scaling into account. Since you already address the meters vs feet you are aware of that. Also it depends on where you put the origin in your object. If you start modeling a building with its origin (0;0 in object space) in the lower left corner then the hitbox parameters could look more like: xMin = 0, xMax = 500, yMin = 0, yMax = 500, Zmin = 0, Zmax = 1000;
When modeling a building always use the floor as Z=0 for best practice; That way you don’t end up with floating buildings or have them sink in the ground. But since I read falcon uses the lowest Z value as the floor, it doens’t really matter I guess.
-
your correct, but you have to take scaling into account. Since you already address the meters vs feet you are aware of that
Aware of what?
-
Aware of what?
That when you export from 3ds to LOD that there is a difference in scaling. If you set meter as units in 3ds your object will be scaled after export so 1 meter becomes 1 feet in LOD. So reading coordinates of vertices in 3ds might be different when you read them in LE.
-
That when you export from 3ds to LOD that there is a difference in scaling. If you set meter as units in 3ds your object will be scaled after export so 1 meter becomes 1 feet in LOD. So reading coordinates of vertices in 3ds might be different when you read them in LE.
hmm As I’m reassured by WaveyDave the master it’s self that created the exporter I use meters in my models and real scale. when I export I leave the selection to feet in the exporter… Everything else is done automatic… I don’t know anything about scale and I don’t touch anything…
When I did something like that my buildings where like for migits and like that they where scaled down…
So Scaling???
Well thanx I’ll pass…
-
That when you export from 3ds to LOD that there is a difference in scaling. If you set meter as units in 3ds your object will be scaled after export so 1 meter becomes 1 feet in LOD. So reading coordinates of vertices in 3ds might be different when you read them in LE.
Just set the scale unit prior to export to 1/1 feet.
Then keep feet in export setup. As you see the size was calculated in meters and fits the city on the map used had some differences from the tile. Some said the buildings look to small… Take in advance altitude. From the ground they aren´t.
-
the look small must be an eye Falcon scaling bug… it’s been discussed to death… no outcome yet. Every 4 years someone comes with arguments on this… it’s like the 3-4 weeks thing… lol
-
Just a teaser xD… I was bored.
-
-
BMARTINS, can you put some ground units on the new object and test how are placed? What about movement through the city?
(The movement problem is not an issue currently, because there is 0 chance to any hostile unit reach this object. :uham:)