Hi we (Tigerpanzer 2003 and Dr.Diode) have released the Beta Map Pantherbase.
We would be very glad about praise and criticism. You can download from this side
http://home.arcor.de/ralphho/pantherbase_beta.rar
Objectives are inside!!! greeetz Dr.Diode
a few bugs/suggestions:
access to this ladder is blocked
you cannot fall through the elevator shafts, getting stuck halfways through.
cannot climb through this window, and others like it.
allies cannot get to elevator controls without a disguised covert ops, the objective is enclosed by team doors
a tower! and a ladder! why can’t i climb it? :???:
command map:
now if any map ever deserved a two level command map, this would be it, one could get lost down there. is this possible?
missing icon for the ehmm… departure signal
it would be nice if ladders to lower level was indicated on command map.
/Had a quick look and some early comments:
Solutions:
good atmospheric setting, i did notice as an allied player when the game starts, i heard the allied vo’s plus the axis ones also.
A few quick comments from me too.
Quite low FPS in some spots, but that’s maybe just normal, I don’t know ?
The guardtower in grid H8 has its roof flicker in and out of existance depending on where you view it from, easiest way to spot that is to sit in the tank and watch the roof as you pass a few meters after the second tankbarrier.
I feel a certain lack of some sound of any kind when you’ve built the tank ramp.
The whole area seems very open to FO airstriking, may be fun, maybe not, I have still not played against anyone on this so I don’t know how building/blowing obstacles will work with that in mind.
I like the exploding barrels near the tank garage, but why not more “extras” that are blowable, like signs, etc, for example the Kommandatur and flag should be blowable/shootable (yes, we like to shoot down unnecessary items… 
)
I agree with the previous posts on cmd map and non-climbable towers
Ok, I’ve just driven the tank across half of creation now I expect it to make me win, not just stand there so I have to spend the rest of the stopwatch-time looking for something I’ve forgotten, so where’s the final obj :???: 
Looking at the obj. desc. it seems there should be some switches to throw, can’t find them, imo that kind of objectives should be placed along the natural “traveling-line” where people will walk when they escort the tank, or near the end (the switched inside the crane don’t work for me at least)
thanks you for the test first time to everyone and i hope my translator translates this for unifier masses well.
What the fps concerns is this one actually in the context of and is in the front area at minimum 50 only still.
Otherwise it always is between 70 and 80-90 fps. I think this is already acceptable.
is changed
still is changed
4., of course invites the free area to the airstrikes and I find it also well so
More explosive things are still installed
Of course it is a paradise to create usable towers for campers, but I think we will open them for Snipers
7., the switch for the signal is in the house next to the train and still is made obvious in the Map
- What the fps concerns is this one actually in the context of and is in the front area at minimum 50 only still.
Otherwise it always is between 70 and 80-90 fps. I think this is already acceptable.
You have to remember not everyone has your computer - what to you may be an acceptable framerate may well be awful on another’s setup. Framerates for me dropped to 40 or so in some places - this is pretty bad for my setup, which is reasonable (amd2400+, 512 ram, gfti4200 w/ 128megs vram). Not top end, but reasonable. I would assume either your specs are much higher, or you haven’t seen the places we have where framerate drops, although they were pretty easy to spot.
I think a responce of ‘framerates are fine for me’ is a very poor response indeed if you wish other people to play your map. It reminds me of one particular thread we had on framerates where it was suggested that the mapper in question should send out a new graphics card with each download of his map since he quite clearly wasn’t prepared to support even mid-ranged setups. It would be the only way many were prepared to play his map!
You have to remember not everyone has your computer - what to you may be an acceptable framerate may well be awful on another’s setup.
I agree, while I may not have the “hottest” graphics card, and also I usually just use default settings (ok I have removed weathereffects, but still otherwise plain default setup…), and depending on the map I can get everything between 90 (good on my PC) down to an average of 45-50 (good enough…), but when fps starts to drop to 20-something I know it’s not good 
(I had 8 on one early betamap a while ago…)
And I still believe I have a fair machine
But anyway it was just a small note to the fact that FPS may be worth checking up, I’m not saying it must be done, but better FPS means more happy players 
And what you may consider terrible others consider excellent… my average FPS is around 20, drops to around 11 on the official maps if there’s a wide open area in front of me, and I manage fine…
I’d suggest putting it a .ZIP file instead of a .RAR file…
more people will have a clue on what to do with it.
You could probably also do without the comments in
the top of the .PK3, but that probably isn’t a problem for
the game… just my script.
And toss the Thumbs.db’s and the other 2MB of bloat. 
Thu Feb 19 12:06:24 CST 2004
Files to analyze:
-rw-r–r-- 1 slick ND80serv 10186938 Feb 8 16:14 panterbase_et.pk3
----- PK3 - panterbase_et.pk3 -----
/home/slick/analyse_pk3s.sh: [: ==================================================: integer expression expected
/home/slick/analyse_pk3s.sh: [: =============: integer expression expected
/home/slick/analyse_pk3s.sh: [: ===========================================: integer expression expected
panterbase_et.pk3 - Minor note: the name “2003” ========" contains spaces which is stupid and will break this script.
/home/slick/analyse_pk3s.sh: [: ===========: integer expression expected
/home/slick/analyse_pk3s.sh: [: ===================================: integer expression expected
panterbase_et.pk3 - ** Legacy warning: the name Dr.Diode"======= contains uppercase letters which should be avoided **
/home/slick/analyse_pk3s.sh: [: ===========: integer expression expected
/home/slick/analyse_pk3s.sh: [: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>: integer expression expected
/home/slick/analyse_pk3s.sh: [: -ne: unary operator expected
/home/slick/analyse_pk3s.sh: [: Beta: integer expression expected
/home/slick/analyse_pk3s.sh: [: -ne: unary operator expected
/home/slick/analyse_pk3s.sh: [: >>>>>>>>>>>>>>>>>>>>>>>: integer expression expected
panterbase_et.pk3 - ** Legacy warning: the name textures/eigen/elefant_tex/Thumbs.db contains uppercase letters which should be avoided **
panterbase_et.pk3 - ** Legacy warning: the name textures/eigen/Thumbs.db contains uppercase letters which should be avoided **
panterbase_et.pk3 - ** Legacy warning: the name textures/eigen/tigertank_tex/Thumbs.db contains uppercase letters which should be avoided **
panterbase_et.pk3 - **** MAJOR WARNING: Unable to locate maps/pantherbase.script’s entity bank_door1 in maps/pantherbase.bsp ****
panterbase_et.pk3 - *** Sound Warning: UNABLE TO LOCATE sound/vo/pantherbase/axis/hq_esctank.wav in sound/scripts/pantherbase.sounds ****
panterbase_et.pk3 - **** MAJOR WARNING: SOUND sound/scripts/pantherbase.sounds REFERENCES NON-EXISTENT FILES (see above) ****
panterbase_et.pk3 - **** IP Warning: scripts/test.shader appears to be stolen from quake3-pak0.pk3
panterbase_et.pk3 - ** Image Warning: UNABLE TO LOCATE textures/festung/alpha_schneeinv.tga IN scripts/test.shader **
panterbase_et.pk3 - ** Image Warning: UNABLE TO LOCATE textures/festung_skybox/festung_clouds.tga IN scripts/test.shader **
panterbase_et.pk3 - ** Image Warning: UNABLE TO LOCATE textures/festung_skybox/festung_sky.tga IN scripts/test.shader **
panterbase_et.pk3 - ** Legacy warning: texture textures/stone/mxsnow0.jpg in scripts/test.shader should use .tga extension (even if .jpg file) **
panterbase_et.pk3 - ** Image Warning: UNABLE TO LOCATE textures/stone/mxsnow0.jpg IN scripts/test.shader **
panterbase_et.pk3 - ** Image Warning: UNABLE TO LOCATE textures/stone/mxsnow4.tga IN scripts/test.shader **
panterbase_et.pk3 - **** MAJOR Warning: SHADER scripts/test.shader REFERENCES NON-EXISTENT IMAGES (see above) ****
panterbase_et.pk3 - *** Warning: File sound/world/rain_hard.wav of size 441274 in panterbase_et.pk3 is in conflict with pak0.pk3 ***
panterbase_et.pk3 - * Minor warning: sound/world/rain_hard.wav - same sizes and modification time - EXCESSIVE BLOAT *
panterbase_et.pk3 - *** Warning: File sound/world/rain_indoor.wav of size 441250 in panterbase_et.pk3 is in conflict with pak0.pk3 ***
panterbase_et.pk3 - * Minor warning: sound/world/rain_indoor.wav - same sizes and modification time - EXCESSIVE BLOAT *
panterbase_et.pk3 - *** Warning: File sound/world/rain_soft.wav of size 441254 in panterbase_et.pk3 is in conflict with pak0.pk3 ***
panterbase_et.pk3 - * Minor warning: sound/world/rain_soft.wav - same sizes and modification time - EXCESSIVE BLOAT *
panterbase_et.pk3 - *** Warning: File sound/world/rain_tent.wav of size 441244 in panterbase_et.pk3 is in conflict with pak0.pk3 ***
panterbase_et.pk3 - * Minor warning: sound/world/rain_tent.wav - same sizes and modification time - EXCESSIVE BLOAT *
panterbase_et.pk3 - *** Warning: File sound/world/rain_trickle.wav of size 441266 in panterbase_et.pk3 is in conflict with pak0.pk3 ***
panterbase_et.pk3 - * Minor warning: sound/world/rain_trickle.wav - same sizes and modification time - EXCESSIVE BLOAT *
panterbase_et.pk3 - *** Shader Warning: Could not locate shader textures/ettest1/terrain.vertex" referenced in maps/pantherbase.bsp ***
panterbase_et.pk3 - *** Shader Warning: Could not locate shader textures/lights/light_tp_m06off referenced in maps/pantherbase.bsp ***
panterbase_et.pk3 - *** Shader Warning: Could not locate shader textures/lights/light_tp_m07off referenced in maps/pantherbase.bsp ***
panterbase_et.pk3 - *** Shader Warning: Could not locate shader textures/lights/light_tp_m08off referenced in maps/pantherbase.bsp ***
panterbase_et.pk3 - *** Shader Warning: Could not locate shader textures/radar/fog" referenced in maps/pantherbase.bsp ***
panterbase_et.pk3 - *** Shader Warning: Could not locate shader textures/radiant/notex referenced in maps/pantherbase.bsp ***
panterbase_et.pk3 - *** Model Warning: Could not locate model models/mapobjects/barrel_sd/barrel_side referenced in maps/pantherbase.bsp ***
panterbase_et.pk3 - *** Model Warning: Could not locate model models/mapobjects/barrel_sd/barrel_top referenced in maps/pantherbase.bsp ***
panterbase_et.pk3 - *** Model Warning: Could not locate model models/mapobjects/light/pendant10k referenced in maps/pantherbase.bsp ***
panterbase_et.pk3 - *** Warning: TOTAL EXCESSIVE BLOAT is 2206288 bytes ***
panterbase_et.pk3 - **** MAJOR WARNING: BSP doesn’t match PK3 name (very confusing) ****
panterbase_et.pk3 - maps/pantherbase.bsp
panterbase_et.pk3 - **** MAJOR WARNING: contains intellectual property protected by non-ET/Radiant copyrights
panterbase_et.pk3 - SUMMARY: 5 Major warnings 6 Warnings 1 IP Warnings 6 Shader warnings 3 Model warnings 5 Image warnings 1 Sound warnings 5 Legacy warnings 5 Minor warnings 1 Minor notes
SiliconSlick
panterbase_et.pk3 - Minor note: the name “2003” ========" contains spaces which is stupid and will break this script.
Slick you lazy swine, sort it
One major bug in this beta map is the fact that if allies destroy the liftcontroller, they essentially wins the game. Because, even if axis repairs it, the loading of ammo onto the tank doesn’t work.
Is that not a scripting error and could be fixed??, thats the only thing wrong with that map…maybe someone will step up and fix that error…whos knows…
I remember more serious bugs in that map that needed fixing. But as I said, I think that noone cares about this project anymore.
