Author Topic: A navmesh problem of the FH2.4  (Read 1391 times)

Offline zxx43

  • Jr. Member
  • **
  • Posts: 69
    • View Profile
A navmesh problem of the FH2.4
« on: 12-08-2011, 08:08:29 »
I have exported the navmesh of Bastogne.But when I run the BFEditor to repair the navmesh the editor crashed.
Then I run the editor to export the mesh of Vossenack the editor crashed again!
I want to ask whats the matter? ???
Hallo,Mein name ist zxx43.
Ich kommst aus Südchina.
Ich bin 21 jahre alt.
Ich liebe gelesen buch und spielen fussball.
Mein Deutsch ist gut nicht.

Offline cannonfodder

  • Full Member
  • ***
  • Posts: 1.228
    • View Profile
Re: A navmesh problem of the FH2.4
« Reply #1 on: 12-08-2011, 10:08:48 »
Remick did mention he was having trouble with the Bastogne mesh.

I think it was a memory issue... :-\

Offline djinn

  • Masterspammer
  • ****
  • Posts: 5.723
    • View Profile
Re: A navmesh problem of the FH2.4
« Reply #2 on: 12-08-2011, 16:08:43 »
Bastogne, I get. Vossnack? It seems rather ordinary for the most part

Offline Remick04

  • Moderator
  • ***
  • Posts: 103
    • View Profile
Re: A navmesh problem of the FH2.4
« Reply #3 on: 14-08-2011, 23:08:32 »
Bastogne was quite the uphill battle. I spent weeks wrestling with the editor having it constantly crash on me. You could try a 'mass weld' of all vertices in 3Dmax (if you use it). That seemed to do the trick for me. But I also spent weeks cleaning up the navmesh and deleting areas I didn't think the bots would ever go, or weren't important to the gameplay of the map. So, I don't know what I did exactly but once I had a bug free version of the mesh working ingame I kindda decided not to touch it anymore.

Vossenack is deceivingly not ordinary. It looked like it would be easier and less trouble than Bastogne, but it isn't. It took longer to generate than Bastogne (Bastogne = 74 hours 56 minutes and 32 seconds, Vossenack = 135 hours 16 minutes and 14 seconds) and seems to have just as many issues. And unfortunately none of the lessons I learned from Bastogne seem to be helping me with Vossenack. So I temporarily moved on to Hurtgen Forest, because I don't have the energy for another uphill battle right now.

Vossenack will crash when it reaches the generate GTS Data portion of the create navmesh process because there is an object on the map with collision mesh issues. I believe on Vossenack it is the vossenack church windows that cause this problem. Just delete them and it should generate fine. Be careful I believe there are a few static objects that somehow ended up on the gameplay layer (layer 2), like half the trenches in the little trench system on the map. I'm not sure if the generator takes these into account but if you haven’t caught this already I suggest making sure all statics on the map are on layer 1.

Offline zxx43

  • Jr. Member
  • **
  • Posts: 69
    • View Profile
Re: A navmesh problem of the FH2.4
« Reply #4 on: 15-08-2011, 07:08:24 »
ok,i will try it.thanks!
Hallo,Mein name ist zxx43.
Ich kommst aus Südchina.
Ich bin 21 jahre alt.
Ich liebe gelesen buch und spielen fussball.
Mein Deutsch ist gut nicht.

Offline Raziel

  • Jr. Member
  • **
  • Posts: 859
  • Bullet Magnet
    • View Profile
Re: A navmesh problem of the FH2.4
« Reply #5 on: 17-08-2011, 08:08:32 »
Thanks for trying to fix the problems Zxx43
Appreciate it!