Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Fafire

Pages: [1]
1
Newbie Help (Start Here) / Re: Planeshift Setup Program
« on: August 10, 2006, 02:29:30 am »
It would be helpful if the program had pre-sets built in, as many games do ('High Quality', 'High Speed' etc.)

The advantage to keeping all maps loaded is that it saves having to wait every time you pass from one map to another, of course, but it will mean a performance hit since all the maps need to be stored in memory. Keep it off.

Multisampling (Antialising) refers to the graphics card rounding off jagged images by rendering polygons more than once or something like that. It is a big deal for lower end cards, and really old ones can't  handle it at all. If you want to raise fps, keep it at 0 or a low number. (The higher the number, the more passes the graphics card has to make). Don't check 'multisample for quality'.

I am not quite sure what texture downsampling is, but from the name it suggests to me that a texture of say, 160x160, is reduced to half, quarter or whatever. This means that the textures (the 'paint' on the polygons, like bricks, faces of characters) etc. will look worse - less detailed, more blurry. But, you will save a lot of memory in both loading them, and it will require less of your system to render them thus resulting, I think (someone will correct me if I'm hideously wrong) in a performance boost.

If fps is a real problem, there's nothing quite like reducing screen resolution and color depth, but please check other forum posts (possibly in the problems in game list) because I understand that the CS engine is particularly bad: this from the sticky on there ('known fixes'):

Quote
Here are a few things you can do to help your system handle problems on your side:

    * Update the game and your graphics card drivers.
    * Don't use 16-bit color depth.  CS just doesn't work well with it.
    * Try enabling the adaptive distance feature in the options menu. It'll try and maintain a framerate by not rendering farther away objects.
    * Try lowering the graphics settings in lower right of the setup application.
    * You can always try lowering the game's resolution in the setup.  If you can't play with 800x600 or even (the horrid) 640x480, and you've tried everything else, ask for help.

See here: http://hydlaa.com/smf/index.php?topic=21503.0

Good luck!

2
Newbie Help (Start Here) / Re: Help With Death Realm
« on: August 10, 2006, 02:16:22 am »
Ask for advice in-game, posting spoiler information here is frowned upon.

3
Okay, I will keep a tab on the number of users. Thanks.

S.

4
Welcome.

1) is already known and fixed - see http://bugs.hydlaa.com


Could you specify the bug ID? I am running the most updated Linux client and am experiencing the same problem the OP referred to. I am lamentably bad at searching, and as such have been unable to find the entry on bug tracker.

5
I would say at least half the time, and would be prepared to go up to 80% of the time. It is a constant I have noticed, as I said, since the upgrade. I only played PS a little on the previous version, but never once did I experience the lag I now seem to get.

Additional env information: Linux From Scratch, i386, (proprietary) nVidia drivers

6
Actions: Using the chat box for npcs or pcs, more often when initiating a dialogue but sometimes also in the middle of one
Symptoms: Seems more laggy in 3.0.015 than in 3.0.013. A good five to ten seconds pass between posting chat and it actually appearing in the client GUI chat box.
Environment notes: Very fast broadband connection (4 Megabit), based in UK

Should I report this in bugtracker? I checked through the forums but I haven't been here long and I am unsure as to whether this is a known or recognised issue or not.

7
Guilds Forum / Re: [guild] Wrath of Azure
« on: July 23, 2006, 12:24:21 am »
Just a quick note to add the forum url:

www.yliakumknights.myfreeforum.org

[EDIT: Typo in original post]

8
Encountering the exact same symptoms on the latest version (3.0.015). A previous bug report for 3.0.013 (ID 1541) was closed on a "Works for me" resolution, so I have opened a new bug (ID 1965).

It's pretty annoying, that's for sure.

Pages: [1]