IPB

Welcome Guest ( Log In | Register )

Manually navmeshing from the editor?
Dnamro
post Mar 9 2008, 08:43 AM
Post #1


CinC (for now)
Group Icon

Group: Mr. Admin
Posts: 5,813
Joined: 28-December 03
From: Fort Hood, TX
Member No.: 46



I remember reading a post where someone had mentioned that they generate navmeshes from the editor manually, but they did not explain how. Can someone explain how?


--------------------
No, my Avatar is not my dog.
Go to the top of the page
 
+Quote Post
2 Pages V  < 1 2  
Start new topic
Replies (15 - 16)
clivewil
post Mar 12 2008, 10:48 PM
Post #16


Relic
Group Icon

Group: Mr. Admin
Posts: 2,007,406
Joined: 24-July 07
From: Perth, Western Australia
Member No.: 3,545



QUOTE
How did you get that aerial height map to load up in PS? When I try, it just tells me that the file type is not supported.

change its suffix to .raw and then open it as 128x128, 16-bit, 1 channel, IBM PC, which should give you a header size of 20. when it opens it will look completely black, so go Image > Adjust > Auto Levels and it will bring up the detail. if it's still hard to make out, try auto levels again

the above settings are for the average scale 2 map - scale 4 maps are 256x256, etc. etc.

QUOTE
and if the objects are too high above the ground, they won't generate any GTSdata files, so they won't be navmeshed and therefore can't be included in the Aerialheightmap. So mountains may be needed.


you should be able to daisy-chain some statics into a link between the object and the terrain so it appears as being continuous instead of separate, then delete them later after building the .ahm - or as you say, build terrain spikes and then restore the original terrain after genning the .ahm


--------------------
Go to the top of the page
 
+Quote Post
Dnamro
post Mar 15 2008, 10:52 AM
Post #17


CinC (for now)
Group Icon

Group: Mr. Admin
Posts: 5,813
Joined: 28-December 03
From: Fort Hood, TX
Member No.: 46



I will give that a try.

It looks to me like using the generatepathfinding button in the editor does the same thing as running the command AI, exportGTSMeshes. Now, if this is true, then if your following Kysterama's AI tutorial, after you successfully use the generatepathfinding button in the editor, you don't need the exportGTS step in the generateNavmeshLocal python code. Furthermore, all you need to do at this stage is the generateNavmesh function. We don't to want create qtrfiles until after we have verified that we have good infantry and vehicle navmeshes.

Basically after we generatePathfinding (which creates the \GTSdata\mesh folder and data) in the editor, we won't need the editor again, until after we verify that we have good infantry and vehicle navmeshes and are ready to create the Aipthfinding files used by the game.



--------------------
No, my Avatar is not my dog.
Go to the top of the page
 
+Quote Post

2 Pages V  < 1 2
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 21st May 2013 - 07:34 AM