cRPG
Beta => WSE2 Beta => Resolved Issues => Topic started by: DaveUKR on September 05, 2012, 04:49:23 pm
-
Is the client ready to go? We didn't find any bugs for more than 2 weeks. Can you please add some shit to make this client broken?
-
It's almost ready to go. I will work some more on optimization for low end graphics cards, then we plan to release the client as opt-in (until stable for everyone).
If you'd like me to add some more game breaking bugs, feel free to suggest new settings to add or client-side features... :D
-
Well, there are some client-side things which would be great.
- First of all, give the ability to set a separate key for a whistle because it makes you impossible to use other keys while using quest menu and it paralyse you for 1-2 seconds. I know, it's a buff to cavalry but still 8-)
- Separate keys for some voice commands would be awesome aswell
- Admin chat key is still mentioned as Inventory window in key-set
- Water is still dark (almost black) for some reason
- Horse sounds should be louder
- Would also like to have some usable animations (to show attack direction, greet someone etc.)
- Different crosshairs for different bows/xbows (and mb no crosshair for 1wpf crossbow users?)
- different sounds for different ground type
- different sounds for different armour type
- ability to convert skills/attribute in game character menu
- drop all weapons/ammo button
- more diversity with weather (more types of weather: different types of rain, lightening strikes, desert storms etc.)
- setting to use LODs or not and mb define a distance of it
- toggle on/off battalion flags
- sounds for siege equipment, gates, doors etc
And lots of other things.
-
Different crosshairs for different bows/xbows (and mb no crosshair for 1wpf crossbow users?)
Most of Daves suggestions I can take or leave, but this good. Very good. Maybe make it a staggered increase upto 50wpf for arberlest. (a pro arberlest user will manage at least 50 wpf by the time he has the strength requirment)
-
Those are nice suggestions, but all of them except a few are implemented or require changes in the mod, not in the client.
- drop all weapons/ammo button
Will add this.
- setting to use LODs or not and mb define a distance of it
The character detail setting should do that (despite the name it acts as LOD distance slider for all objects, not just characters).
-
1. Can you add more options to disable individuall HUD elements as proposed in this thread? (Take note on the poll results)
I can add a client option to disable gold and health (because they're shown by the client), but I can't add an option to disable experience or multiplier (because they're shown by the mod).
2. Can you edit the graphics profile options so it contains more profiles?
I am asking this because, if you add more choices, it will be easier for bug reporting - client optimization. You can tell people to select the X profile, and than report. I hope I am making sense...
You are making sense, although I'm not sure it would help much. Most setting have 3/4 tiers, so the current amount of presets is enough to try them all...
-
Maybe add a setting to choose default sounds/More Metal Sounds ? Is it a client side ?
-
No, it's done in the mod files.
-
Ever since I first used the launcher, despite the bugs that were present, I have not had a single crash of warband during play. Since I love ALT TAB a lot, and I dislike crashes that lose my x5, this has been thus far awesome. It made the game a lot more enjoyable for me.
What I'm trying to say is:
a/ release it to everyone (as open beta) - you'll help a lot of people enjoy the game more, and they can always switch back until all the edges are ironed out
b/ awesome work
-
If possible: please PLEASE add a "dismount horse" button. It's very annoying trying to dismount a horse and accidentally picking up weapons instead, getting yourself killed in the process.
-
what about drop all ammo/weapons button? How is it going?
-
Not possible without breaking server compatibility.
-
Not possible without breaking server compatibility.
is it something that should stop you? :wink:
-
Yes, since it means that people without the beta client won't be able to connect to servers anymore.
-
Yes, since it means that people without the beta client won't be able to connect to servers anymore.
mb there is a reason to make a separate server for beta clients to test it and then implement it for everyone.
-
Nah, we'll talk about breaking compatibility after the beta client is properly tested and used by everyone.