Page 1 of 1
Boundary Problem and Award Weapon Glitch [Solved]
Posted: Tue Jun 23, 2009 9:52 am
by MandeRek
Well, I'm trying to add a boundary to my map but it's not completely working..
BZP.req
Code: Select all
ucft
{
REQN
{
"config"
}
REQN
{
"boundary"
"BZP"
}
REQN
{
"texture"
"BZP_map"
"water_bumpmap_0"
"water_bumpmap_1"
"water_bumpmap_2"
"water_bumpmap_3"
"water_bumpmap_4"
"water_bumpmap_5"
"water_bumpmap_6"
"water_bumpmap_7"
"water_bumpmap_8"
"water_bumpmap_9"
"water_bumpmap_10"
"water_bumpmap_11"
"water_bumpmap_12"
"water_bumpmap_13"
etc...
In ZE, i added a boundary named 'boundary'.. Ideas?
Also, I've got the problem of my weapons, that the game freezes when switching them..
I added this to my weapon odfs:
Code: Select all
ScoreForMedalsType = -1
MedalsTypeToUnlock = -1
Will that do it?
Re: Boundary Problem and Award Weapon Glitch
Posted: Tue Jun 23, 2009 10:05 am
by DarthD.U.C.K.
you have to call the boundary in ZE "BZP" i think
Re: Boundary Problem and Award Weapon Glitch
Posted: Tue Jun 23, 2009 10:08 am
by 501st_commander
the
ScoreForMedalsType = -1
MedalsTypeToUnlock = -1
will do that. I've used it many times.
Re: Boundary Problem and Award Weapon Glitch
Posted: Tue Jun 23, 2009 10:35 am
by Fiodis
Only it's not working for him.
How about setting those two values to extremely high, unrealistic numbers instead?
Re: Boundary Problem and Award Weapon Glitch
Posted: Tue Jun 23, 2009 11:43 am
by FragMe!
you also need to create a region and make it's type mapbounds, you can also name it mapbounds if you want.
Re: Boundary Problem and Award Weapon Glitch
Posted: Tue Jun 23, 2009 11:47 am
by MandeRek
FragMe! wrote:you also need to create a region and make it's type mapbounds, you can also name it mapbounds if you want.
Man... I haven't spoken to you in months
So a big, boxy region named mapbounds, which can be seen as my boundaries? No including in req for this region?
Re: Boundary Problem and Award Weapon Glitch
Posted: Tue Jun 23, 2009 12:19 pm
by AQT
MandeRek wrote:Also, I've got the problem of my weapons, that the game freezes when switching them..
I added this to my weapon odfs:
Code: Select all
ScoreForMedalsType = -1
MedalsTypeToUnlock = -1
Will that do it?
Don't use those lines
at all. Make weapon .odfs that don't have class parents. For example
and
You see? No class parents! You won't earn medals but at least your game won't freeze.
P.S. Didn't I already send some class parent-free weapon .odfs to you? The day after the Alpha? Oh well.
Re: Boundary Problem and Award Weapon Glitch
Posted: Tue Jun 23, 2009 1:51 pm
by MandeRek
Yeah you did send me those.. But more weapons were having that glitch I guess.. Classparent free weapons.. That will be A LOT OF WORK
But okay.. I'll fix it
Thanks AQT!
Btw, do you know anything about leaving-battlefield-messages? My boundary is still not working, even with the mapbounds region
Re: Boundary Problem and Award Weapon Glitch
Posted: Tue Jun 23, 2009 2:20 pm
by AQT
You're welcome.
As for the boundary issue, well I got the message to work in my map. What I did was:
1. Placed a boundary in my map and named it "boundary1" (no quotes)
2. Edited my map's .req to include the boundary the same way you did but it was the second to last thing in the .req (before my map's mini-map texture)
3. Made a mapbounds-type region called "mapbounds" (no quotes)
Doing all these things got message to work. Make sure your .bnd and .pth files are being saved.
Re: Boundary Problem and Award Weapon Glitch
Posted: Tue Jun 23, 2009 4:45 pm
by AceMastermind
To make a working boundary read this:
http://www.gametoast.com/forums/viewtop ... 02#p219402
You don't need a mapbounds region to get your boundary working.
Re: Boundary Problem and Award Weapon Glitch
Posted: Tue Jun 23, 2009 5:06 pm
by MandeRek
Read that, but had problems, which is why i made this topic. I changed the name from boundary 'boundary' to 'boundary1' and now it's working?
Anyhow, this topic can be locked! Thanks for all help, all!
Re: Boundary Problem and Award Weapon Glitch
Posted: Tue Jun 23, 2009 5:31 pm
by AceMastermind
MandeRek wrote:I changed the name from boundary 'boundary' to 'boundary1' and now it's working?
Much like the other fellow in that topic, you probably had it right to begin with but the req or something else may not have munged, but when you made another change VM picked up on it.
A manual clean and re-munge may have gotten your original setup to work.