High Res Tectures Back!!

[Duffman]

Weekly Dev Activities update is coming today, if that's what you mean. Sitting down to work on it now.

High
Res
Textures


http://boards.station.sony.com/ubb/planetside/Forum16/HTML/002484.html

[Queensidecastle]

eh? I didnt know they were gone. I have had all graphical details set to max since December and havent noticed a drop in quality..

[Duffman]

tahts because they were gone in a November patch

[Biohazzard56]

I never remembered Hi-Res Textures, good for people with really fast comps, i have a good machine but im not going to run them. Devs please optimize Planetside more, like heavily

[Ghryphen]

This is what's in QA at the moment. You already saw much of it last week. This is a big update, so there's a lot of work to be done before it is ready for the live servers.

Changes from Last Week's Report

High Resolution Textures: The Programmers believe they have fixed this issue and hope to release the fix along with the rest of this update. However, I have to remind the community that this is the first time the fix has entered QA, and so there is potential for it to be delayed until the next update. We're hoping that's not the case though because we know how much the community wants to see them again.

Infiltrators and the Flail targeting lazer: As we discussed last week, the previous explanation was misleading. Infiltrators will not become more visible when using support equipment. Rather, we have fixed a bug that prevented the Infiltrator from becoming partially visible when using the Flail's targeting laser.

Magrider Brakes: SmokeJumper sent me more information on this change, and how it affects more vehicles than just the Magrider and also improved torque on some.

Spork's Pre-Emptive Response: We're not ready to discuss any decisions on the balance topics going around, so they are not listed here.

Gameplay

Capitol Buildings are currently in our internal testing. Read more about them In Development.
If a Cavern is locked, then any friendly surface facilities connected to that cavern (via the lattice through the Geowarps) will act as if it had all six modules installed.
Hand-held AT weapons now have "recharge capacitor units" (Ancient Tech "ammo") that you can buy at AT equipment terminals or at facilities with the Equipment module benefit.
Phalanx Wall Turrets now have a great upward pivot, allowing them to more easily targeting incoming aircraft.
Certification Terminals can now be destroyed.
Double-clicking on a Warpgate will now zoom to its linked continent.
Hand Grenades will now come in clips of three, though they will require the same amount of inventory space as before. i.e. A clip of three grenades will take up the 2x2 inventory space that a single grenade consumed before.
TR Burster will only do direct damage to non-aircraft targets. It will no longer inflict splash damage on infantry and ground vehicles.

Bug Fixes

High Resolution Textures will display properly again.
Enhanced Targeting will now show the status of enemy Flails beyond 15 meters.
Fixed a bug that was causing Infiltrators to remain completely invisible when using the Flail's targeting laser. Infiltrators will now be as visible when using the Flail laser as they would while using any other piece of support equipment.
Pistol slot items will no longer be visible in an Infiltration Suit.
Hotswapping items will no longer cause infiltrators to become more visible.
The Infiltration Status Icon will function properly, giving a visual indicator of how "cloaked" a player is.
The nature of the Empire-specific Infiltration Suit models caused some suits to be more visible than others. We have adjusted parameters for each Empire to compensate for this.
Damage Decals will no longer show up on water.
Scorch decals on a door will not remain stationary when a door opens.
Fixed an issue that would cause players to lose Outfit points.
Outfits can invite players with a �J or �K appended to their name through the Outfit Window.
Fixed an issue where newly created characters could not receive send or receive /tell messages or be added to friends list.
Teleporting through Router telepad will no longer cause Darklight to appear with normal field of vision.
Energy weapons will leave a damage decal on surfaces again.
Wall Turrets that are destroyed and repaired will display the proper textures.
Drivers will no spawn in a vehicle with only 1 shot remaining in the vehicle�s weapon clip.
Manual binds will no longer remain after deleting character and creating another.
Fixed an issue where an avatar could remain in the world after being disconnected.

Other

Levels of visibility have been honed for each of the different actions that Infiltrators can take � running, walking, crouch-walking, jumping, and shooting, etc. Further, the level of visibility has been adjusted to account for multiple simultaneous actions, such as jumping and shooting.
Infiltrators will remain cloaked when they mount a vehicle, but will be partially visible as long as they occupy the seat. This adjustment does not apply to the wraith, which will remain fully invisible when sitting still, and become more visible at higher speeds.
A glow effect and a laser sight effect have been added to the Decimator.
Wheeled and Treaded brakes were adjusted in order to allow shorter stopping distances. Vehicles affected: Harasser, Skyguard, Enforcer, Marauder, Lightning, ANT, Deliverer, AMS, Sunderer, Vanguard, Prowler, Wraith, Basilisk. (NOTE: Gearboxes have been tuned to allow "rolling" on hillsides. If the vehicle driver desires to stay in a single spot, simply apply the brakes (spacebar) and the vehicle will stop unless you're on a particularly steep hillside.)
Hover vehicle brakes were modified to allow brakes to function more efficiently. Vehicles affected: Magrider, Thresher, Router, Flail, Switchblade.
Low-ratio gears (first and second gears) were adjusted (slightly) on the following vehicles in order to increase their torque (starting power) when trying to start moving uphill from a dead stop. Vehicles affected: AMS, Sunderer, Vanguard, Prowler, Magrider, Router, Flail.

[ORANGE]

yeah lets concentrate on bugs and crap first plz

EDIT: Fixing the acceleration on the prowler finally thx be to SOE

[Biohazzard56]

What significance does being able to destroy certification terminals have?

[BigFreak]

Woo for high res textures \o/

[GreyFox]

What significance does being able to destroy certification terminals have?Maybe easier to drain a Bio Lab from its NTU?

[dscytherulez]

What significance does being able to destroy certification terminals have?

Little to none.

[Madcow]

I'm excited for this to get to the test server. Nothing has previously gotten me on to the test server, although I've been patching it every once in a while to make sure I didn't get whammied with a monster patch.

[Kaymon]

What significance does being able to destroy certification terminals have?

I wonder why they wrote this in there. I've been destroying cert terminals since July. Bio labs were notoriously easy to drain, even after the matrix panel fix. 2 Decis = dead terminal.

Seriously, you can do that already.

[KIAsan]

Spork's Pre-Emptive Response: We're not ready to discuss any decisions on the balance topics going around, so they are not listed here.


CRAP, not another patch before they fix the lasher. It's starting to get really frustrating (more so than a quad shot JH).

[infinite loop]

This is an absolutey the biggest fucking joke ever. The lasher bug is killing the game, yet it isn't their top priority? Whoever their project manager and business analysts are they should all be fired.

[SilverLord]

Whoever their project manager and business analysts are they should all be fired.I totally agree with that statement. I also want them to optimize some FPS issues and studdering with the low end systems. Whe I am looking at a wall and nothing there, i shouldn't be getting only 60 frames.

[ORANGE]

I totally agree with that statement. I also want them to optimize some FPS issues and studdering with the low end systems. Whe I am looking at a wall and nothing there, i shouldn't be getting only 60 frames.
Holy crap your getting 60 fps im hanging around 20-30

[Kaymon]

This is an absolutey the biggest fucking joke ever. The lasher bug is killing the game, yet it isn't their top priority? Whoever their project manager and business analysts are they should all be fired.

Note: the following is not a real flame. I repeat, I am not flaming you in any way.

With an attitude like that, you will remain on the bottom of the corporate ladder. The best paying jobs you will ever have will involve either a shovel or a wire brush. Unfortunately for the rest of us, that's still enough for basic internet access.

/not flaming, really

Ok, my real reply:

They can't jump around like that with their bug fixes. Rash decisions aren't met well by management, and code fixes like what are required usually take awhile to get through QA without introducing even more bugs.

Rushing a patch only invites disaster.

[SilverLord]

I dunno what the devs are thinking...High Res tectures are much more important that accually letting poor people get some lovin.

[Rbstr]

well high res textures are more of a vidoe memory thing than a power thing.

[Happy lil Elf]

You're whining about 60fps? /boggle

Tell ya what, get back to me when it hovers around 7-11fps and you can get all the way up to the 20s if you're in the middle of an open field staring at the ground.

Sad part is I still hover around 45-50fps (15-20fps in large fights) and I'm now playing on a-
AMD 3k
1.5GB of PC3200 400mhz
9800 Pro 128mb card

[infinite loop]

Note: the following is not a real flame. I repeat, I am not flaming you in any way.

With an attitude like that, you will remain on the bottom of the corporate ladder. The best paying jobs you will ever have will involve either a shovel or a wire brush. Unfortunately for the rest of us, that's still enough for basic internet access.

/not flaming, really

Ok, my real reply:

They can't jump around like that with their bug fixes. Rash decisions aren't met well by management, and code fixes like what are required usually take awhile to get through QA without introducing even more bugs.

Rushing a patch only invites disaster.

Ok, not really sure where you were going with that first statement, that's just odd. Anyway, I'm not interested in moving up any corporate ladders. Management isn't my thing, I like doing actual work.

As for the second part, I never mentioned that I wanted them to rush out any patches. Just that fixing the lasher should be top priority, whether it takes a week to fix, or 2 months. I just want acknowledgement that they have some kind of logical priorities for bugs and patches. Competent management would realize what is best for the customers, and work on that first, but obviously they're not. No offense, but the code fixes we're used to seeing in PS usually introduce as many bugs as they fix. Seems the QA department should be fired too.

[Duffman]

did you guys also see they are putting back the no lash within 5m

[Deadlock]

Never missed the high res. textures... BEING THAT I CANT RUN THEM AND MOVE MY CHARACTER AT THE SAME TIME!!!... stupid poor'ness, god i cant wait for that tax refund

[DemiInuyoukai]

heh, the person that has annoyed you people so is back

[Warborn]

You're whining about 60fps? /boggle

Tell ya what, get back to me when it hovers around 7-11fps and you can get all the way up to the 20s if you're in the middle of an open field staring at the ground.

Sad part is I still hover around 45-50fps (15-20fps in large fights) and I'm now playing on a-
AMD 3k
1.5GB of PC3200 400mhz
9800 Pro 128mb card

Sounds like me. PS's performance leaves a lot to be desired.

[SquirrelMan]

I totally agree with that statement. I also want them to optimize some FPS issues and studdering with the low end systems. Whe I am looking at a wall and nothing there, i shouldn't be getting only 60 frames.

WOW! 60 FRAMES?! Man, I envy you. I NEVER get that much.

[SilverLord]

Guys...i meant only 60 frames looking at the ground or a wall with nothing else going on. In zergs it goes down to like 10-15.

[KIAsan]

They can't jump around like that with their bug fixes. Rash decisions aren't met well by management, and code fixes like what are required usually take awhile to get through QA without introducing even more bugs. Rushing a patch only invites disaster.
Hmm, ok, I will believe that when they stop rushing through change patches. The lasher changes is a very good example of this. NOWHERE did they mention they were changing the lash distance. Then poof, its in the game and bugged beyond belief. Heck, they were even confused to whether the lasher change was a parameter change or a code change, AFTER they had changed it. However, this may all be OBE according to Duffman's post (POST the link please sir).

BTW, my intention is not to flame the devs, they have a hard enough job. But for just once, I wish they would really fix the bugs in the game FIRST, then worry about introducing new content (AFTER extensive bug testing).

Edited to correct the quote.

Edit x2: Found the note from spork:

posted 03-01-2004 04:31 PM user search report post
--------------------------------------------------------------------------------
We're going to be implementing the Lasher's 5m before lashing restriction. The other bugs are in the QA database for verification, debugging and resolution. However, I do not have a timeframe yet. Same goes for the lock-on issues.
As for the Implant balance pass... Renaming an implant requires a person who knows how to open a text document and change a word. Changing an implant's behavior requires a significant amount of time from a Programmer.

[Kaymon]

Hmm, ok, I will believe that when they stop rushing through change patches. The lasher changes is a very good example of this. NOWHERE did they mention they were changing the lash distance. Then poof, its in the game and bugged beyond belief.

This is taken straight from the patch notes:

Lasher
The Lasher's clip size is being increased to hold 25 rounds, and its reload time is being shortened. The Lash effect will no longer be restricted at ranges of less than 5 meters.

Found here:
http://planetside.station.sony.com/game_updates/development.jsp?category=Game&id=60684

If you're trying to debate with me, it would do you well to do your homework instead of looking like an ass.

[Duffman]

However, this may all be OBE according to Duffman's post (POST the link please sir).

its in the rest of the thread

i saw your edit too just posting for others too see

[KIAsan]

This is taken straight from the patch notes:



Found here:
http://planetside.station.sony.com/game_updates/development.jsp?category=Game&id=60684

If you're trying to debate with me, it would do you well to do your homework instead of looking like an ass.

Hmm, didn't realize that posting my comments required I debate you, I am merely posting my opinion. But in a self-centered world that revolves around the forum star that is Kaymon, I'm sorry I didn't rise to your level of debate. Next time I promise to do my homework, oh superstar of the forums, Just please, please, please don't wound me so aggregiously next time by calling me an "@$$". Oh the humanity, I have been shamed by the greatest of flamers on this board. I bow to your superior intellect, please feel free to correct everything I post from this point forward. Not.


Now back on subject, when I talk about it not being mentioned, I am talking about what was common knowledge of the "in concept". I recall reading about all the other changes, not the lash within 5 meters. That showed up once they went to test (which in this world is pretty sudden). As to my comments about the the devs not knowing if it was a parameter vs a code change, that stands as is. Spork has on at least two occasions referred to the lasher as a "simple parameter change" and then a "complex code change", depending on how he was defending the patch/bug fixes. Sounds like they worked it out.

As to your contention that we should give the devs a pass on bug fixes because they can't "rush changes", well that would cut some weight, except their history is very poor on this. Every patch they release is bugged. So, why don't they hold up capitols, etc to hunt down and fix the bugs in-game first? This would also give them more time to debug the upcoming patch. I can guarantee we will all be here soon talking about the latest bugs in the upcoming capitol patch (which will be in test tomorrow). Talk about rushed! I won't state the obvious reasons (money), but let you draw your own conclusions ($$$$).

[Kaymon]

Hmm, didn't realize that posting my comments required I debate you, I am merely posting my opinion.

You quoted me, and tried to counter me. That's what debate is. This might help:

http://dictionary.reference.com/search?q=debate

Once again, please, if you're going to try to argue, or debate with me, do your homework.

[dscytherulez]

You're whining about 60fps? /boggle

Tell ya what, get back to me when it hovers around 7-11fps and you can get all the way up to the 20s if you're in the middle of an open field staring at the ground.

Sad part is I still hover around 45-50fps (15-20fps in large fights) and I'm now playing on a-
AMD 3k
1.5GB of PC3200 400mhz
9800 Pro 128mb card

:huh:

I have that exact same system, except I only got a gig of RAM and it's only PC-2700. I rarely, if EVER, dropped below 30 FPS. Even in huge zergs. I'd think you should be doing better than that.

[KIAsan]

Ok, was going to resist, but what the hell, lets get into a pissing contest. The post that kicked all this off was my post:


Hmm, ok, I will believe that when they stop rushing through change patches. The lasher changes is a very good example of this. NOWHERE did they mention they were changing the lash distance. Then poof, its in the game and bugged beyond belief.


Your response:
This is taken straight from the patch notes:

Found here:
http://planetside.station.sony.com/game_updates/development.jsp?category=Game&id=60684

If you're trying to debate with me, it would do you well to do your homework instead of looking like an ass.

Now if you will examine your post, you imply that we were given notification in the patch notes. Now, patch notes are released with the patch. So, if they put a change into effect, then make a statement they put it into effect, that does not equal prior notification. Nowhere in your statement is a counter to my original argument that they DIDN'T tell anyone prior to testing. This was not in concept to my recollection. Now, if you have any evidence that this was discussed PRIOR to them putting it into the game, then by all means post it and prove me wrong. However, may I suggest, don't bother, since I really don't give a rats ass about the mecanics of how SOE screwed up yet another patch, nor do I give a rats ass in continuing to aide you in this bit of written mental masturbation. I will go ahead and declare your the champion flame baiter of this thread, you hereby win a gold star and a cookie. So please quit posting in this thread (since we are WAY off topic). Apologies to all for me doing the same.

The fact still remains, SOE screwed it up, they know its screwed up, they are working to fix it, and will screw it up again. Hey, maybe I should just make this my signature.

[Kaymon]

However, may I suggest, don't bother, since I really don't give a rats ass about the mecanics of how SOE screwed up yet another patch, nor do I give a rats ass in continuing to aide you in this bit of written mental masturbation. I will go ahead and declare your the champion flame baiter of this thread, you hereby win a gold star and a cookie.

Personal insults are the last bastion of those who lack a good arguement. Meanwhile, you still fail to realize that we got all the patch notes before we got the patch. Spork posts them on a forum called "Development Discussion". Then they go onto the test server. The public test server, so not only can you read about it, but you can see it first hand before it goes live. To say that anything was unannounced shows that you are ignorant of the volumes of data the Planetside team gives us. Such ignorance can be cured by doing your homework.

I would reccomend you do some research, look at all the information that is made available to us. Places like the In Concept, In Testing, and Development Discussion section of the PS forums. Barring any ability to get onto the test server, the test server forum as well.

Once you have done this, then you can come back and post again. Because your overwhelming ignorance is making me sick.

[321]

Yeah high-res textures are back and yay for me cause I could run them no prob.

[KIAsan]

Ok fine, I give up, lets debate the issue:

Your contentions:
They can't jump around like that with their bug fixes. Rash decisions aren't met well by management, and code fixes like what are required usually take awhile to get through QA without introducing even more bugs. Rushing a patch only invites disaster.

Meanwhile, you still fail to realize that we got all the patch notes before we got the patch. Spork posts them on a forum called "Development Discussion". Then they go onto the test server. The public test server, so not only can you read about it, but you can see it first hand before it goes live.

My Counters:
Hmm, ok, I will believe that when they stop rushing through change patches. The lasher changes is a very good example of this. NOWHERE did they mention they were changing the lash distance. Then poof, its in the game and bugged beyond belief.

� when I talk about it not being mentioned, I am talking about what was common knowledge of the "in concept". I recall reading about all the other changes, not the lash within 5 meters. That showed up once they went to test (which in this world is pretty sudden).

Now, based on my research, the following events occurred:
6 Feb: SporkfirePS in response to a question on the official forums:
The "don't lash close" and the "don't lash friendlies" features are redundant, just as you supposed. Removing the "don't lash close" restriction will likely result in almost no change since the projectile barely has time to create a lash before that limit was reached anyway...but I'll go ahead and remove the "don't lash close" constraint because it's just simply not important anymore.
10 Feb: They announced the test and the patch notes
12 Feb: They went into test
17 Feb: Patch went live

So in conclusion, I stand by my argument. They never talked about this change in concept (which generates the majority of discussion on a patch). The only prior notice of the change (prior to test) was buried in the 6 Feb thread. SOE went from �I don�t think this is going to cause a problem, so I�ll change it� to live release in ELEVEN FRIGGING DAYS!!!!! True, we did have 2 days notice before the patch, and 5 days after the patch before it went live. So I grant you that part of the argument. However, my point is that SOE rushed the lasher change into circulation without taking any time to look at it, all on the basis of a whim by sporkfire. So, SOE can RUSH the frigging fix. That is the only point I�m trying to make. Finally, I am sorry if you have taken personal insult from anything I have posted, I didn�t mean to hurt your feelings and I truly hope you will forgive me. Too bad your own hands are not so clean.

[Kaymon]

Your post was made at Today, 04:15 AM. Don't you have a job?

However, my point is that SOE rushed the lasher change into circulation without taking any time to look at it, all on the basis of a whim by sporkfire.

No, Sporkfire is the PS community rep. He doesn't make any decisions, he sends feedback. Changing the lash distance was a matter of opening a text file and changing a 5 to a 0 (as Smokejumper said). They had playtests after that change was made. They tested the patch.

The problem with the lasher is that there are so many of them now. Minor bugs look giant when 90% of the VS players are using the weapon.

Finally, I am sorry if you have taken personal insult from anything I have posted, I didn�t mean to hurt your feelings and I truly hope you will forgive me. Too bad your own hands are not so clean.

You know, you're right. I don't give a shit if I hurt someone's feelings. I'm not going to pansy my way around someone's emotions when I'm trying to make a point. Hell, if I make someone cry, that means that not only did I make my point, but they had to think about it too. But I'm not going to apologize for it.

[KIAsan]

Dude, you didn't make a point. SOE rushed the change, period. Now they should rush the patch, since it is so simple to fix. The problem is they do something like this without much thought and limited testing, then want to wait to make all the changes at once, to minimize download time. In the mean time, everyone else is stuck getting the uberlashed up there rear end. And I think my sarcasm is a little too dry, will have to work on it. Anyway, time to let this hijacked thread die.

Cool, high res textures are back. Although, I didn't see a lot of them in the playtest.

[Kaymon]

Cool, high res textures are back. Although, I didn't see a lot of them in the playtest.

I see them. They're not as 'hi' rez as they used to be. We got shafted again.

[Firefly]

I demand to know why the Lasher is the only weapon that does not cause friendly-fire damage. "Does not lash friendlies". So, then can the Jackhammer and the MCG have the same effect? Or is completely removing the safety net for NC and TR the feature for Vanu HA weaponry?

PS: KIA lives in Japan. That's close to 12 hours ahead of you.

[Dharkbayne]

That's just the lash, moron, otherwise, it would be a grief machine, you would hit friendlies when you shoot past them.

[Firefly]

I know it's the lash effect you fucking tool. Try to refrain insulting people with more common sense and intelligence than you, Einstein.

Ever hear of the Pounder, you brainless retard? Who gives a rats ass if the Lasher is a grief machine? Only the Vanu- then they can't spam corridors. Why should it be fair for the Vanu, when any OTHER empire shooting past their buddies runs the risk of hitting them, regardless of the weapon? The Vanu have the only grief-free weapon in the game. Explain how that's balanced.

Next time bring something intelligent to the conversation, instead of trying to flame what you can't even compare with.

[Dharkbayne]

Trust me, back in beta, the lasher was a grief machine, it was un useable. it hits EVERYTHING on the way TO the target, pounder only explodes at the target point, doing damage there.

[Firefly]

I know, I was in beta as well.

The damn thing should lash friendlies. If you're standing in front of the firing line, you should damn well suffer the penalties JUST LIKE EVERY OTHER EMPIRE. If you're an ignorant retard and you step in front of someone firing a weapon that explodes, you take explosion damage. If you're in a blast radius, you take damage.

So why the hell does the Lasher NOT do that? That's so unbalanced it's pathetic. The TR Pounder was the same thing, a grief machine. You either played intelligently and didn't spam, or you didn't step out in front of one. If you're a dumbass, you deserve to pay the price. Not just TR and NC dumbasses. They can easily fix that by making it lash on contact, or make the lash a cone effect, so that as it goes further out, it lashes farther. But if you're a stupid moron and go firing a weapon near friendlies, they deserve to die and you deserve the grief. Plain and simple.

It's not fair or balanced that hordes of Vanu can fire the thing in CQB situations and not kill a single one, while the rest of us with HA weapons are equal-opportunity killers.

[Dharkbayne]

it has a 3 meter radius, that means that it hits EVERYTHING WITHIN 3 METERS OF IT. THE WHOLE WAY. Firing with a pounder, you can shoot between 2 friendlies and still hit the target with no grief, but with a lasher, you would have hit BOTH of them on the way. The other HA doesn't HAVE splash damage. And with the CQ lash, a friendly could stand PARRALELL TO YOU AND STILL GET LASHED.

[Firefly]

Which is why I posted an initial solution to the problem instead of bitching about it and offering no solutions about it. Three meters is a hell of a radius to lash shit at- so they can either cone it out, or lash on contact.

I don't care how the damn weapon works- it's a huge injustice that the friggin Lasher doesn't damage friendly troops, when every other weapon does damage. Don't punish the rest of the empires because some GED-having retread fucked up or came up with a shitty idea that only those who suffer at its hands know how to fix.

[Pogostickx]

the lasher dosn't damage friendlys? the last thing i killed with it was a teammate :-/

[GreyFox]

the lasher dosn't damage friendlys? the last thing i killed with it was a teammate :-/
It don't have Lash Friendlies.

[Pogostickx]

oh i see what you mean, direct hits will hurt...but it won't do the "lash" to them.

i never noticed that :doh:

[SlyMarbo]

LOL you two go back and forth about there shafting or not shafting then POOF


Quote:
--------------------------------------------------------------------------------
Originally Posted by KIAsan
Cool, high res textures are back. Although, I didn't see a lot of them in the playtest.
--------------------------------------------------------------------------------


I see them. They're not as 'hi' rez as they used to be. We got shafted again.

[Kaymon]

Well yea, look at the DC switch. That thing was godlike as an AI Max in beta. They switched it, then switched it back, and now it's the French AI Max. Same thing happened with the textures.

[Happy lil Elf]

:huh:

I have that exact same system, except I only got a gig of RAM and it's only PC-2700. I rarely, if EVER, dropped below 30 FPS. Even in huge zergs. I'd think you should be doing better than that.

I get the feeling I should be getting higher fps as well honestly, but I'm not sure what I can do to up it =\

[Madcow]

You're whining about 60fps? /boggle

Tell ya what, get back to me when it hovers around 7-11fps and you can get all the way up to the 20s if you're in the middle of an open field staring at the ground.

Sad part is I still hover around 45-50fps (15-20fps in large fights) and I'm now playing on a-
AMD 3k
1.5GB of PC3200 400mhz
9800 Pro 128mb card

Out of curiosity, what levels are you running your graphics at? I'm on a Pentium 2.4, 9600 xt and I just barely upgraded my RAM to 1 GB (although it's only PC2100) and I'm seeing significantly better performance than that. I am at medium settings on just about everything with flora turned off completely. I would guess if I jumped my settings up some I'd see the performance you're seeing but right now I rarely dip below 35 fps.

[Onizuka-GTO]

I didn't know the lasher "lashes" people even when it flies pass an enemy. thats pretty funky. I like that, its a quirky Vanu-thang.
:lol:
Don't know why your so angry firefly, seems fine to me. Perhaps the Vanu has special Armour that makes it's weapons "friendly" with each other?
:lol:

[Firefly]

I'm not angry about it. I got angry that I was attacked for asking a legitimate question, and then received somewhat of an answer in the form of stupid, basic-level information that EVERYONE knows.

I want to know why there is only ONE weapon that does not grief friendlies with its most important main feature, when the rest of the empires all have NO comparable weapons. Special features are special features. The Jackhammer is a powerful quick-fire weapon that hits hard at close ranges and tears through just about anything. The MCG is a rapid-fire weapon, that's about all it does. It fires the same ammo as most other small arm weapons in the game.

Then there's the Lasher. Its special feature is that it lashes anything along its trajectory at a supposed 3-meter radius. That's great. That's swell, that's a good special feature unique to the Vanu. I don't have a problem with it lashing, I don't have a problem with that as a special feature or that it lashes enemies. I don't care if it doesn't lash in under five meters, that means piss to me. So what if I can get in close? I can back far away from a Jackhammer and blow his brains out with my Cycler.

The key is, the clincher is, IT DOES NOT LASH FRIENDLIES. That's no grief. That's horribly unbalanced. That's more like TWO special features. If it lashed friendlies and enemies, then I wouldn't care. It would be fair and balanced all around. It would also prevent lasher spam, which as you may have noticed is a SERIOUS problem right now.

[Kaymon]

Hey, Firefly, we'd like to keep the empires DIFFRENT, ok? Vanu technology at work. If it lashed friendlies nobody would use it.

[EarlyDawn]

I know, I was in beta as well.

The damn thing should lash friendlies. If you're standing in front of the firing line, you should damn well suffer the penalties JUST LIKE EVERY OTHER EMPIRE. If you're an ignorant retard and you step in front of someone firing a weapon that explodes, you take explosion damage. If you're in a blast radius, you take damage.

So why the hell does the Lasher NOT do that? That's so unbalanced it's pathetic. The TR Pounder was the same thing, a grief machine. You either played intelligently and didn't spam, or you didn't step out in front of one. If you're a dumbass, you deserve to pay the price. Not just TR and NC dumbasses. They can easily fix that by making it lash on contact, or make the lash a cone effect, so that as it goes further out, it lashes farther. But if you're a stupid moron and go firing a weapon near friendlies, they deserve to die and you deserve the grief. Plain and simple.

It's not fair or balanced that hordes of Vanu can fire the thing in CQB situations and not kill a single one, while the rest of us with HA weapons are equal-opportunity killers.Yes, it needs a nerf. Turning it into an energy chainsaw of friendly death is not the way to approach that problem. Nobody used it back in beta because you'd kill more friendlies then enemies.

[delta]

http://boards.station.sony.com/ubb/planetside/Forum16/HTML/002484.html

Yay,
I didn't know they were gone, but yay!

[Rbstr]

I've noticed that it realy acctuualy runs better on P4's (not with HT on) by a very reasonable amount

that could accout for some things