Soldat 1.6.0 Release Candidate

[ExHunter]

That's quite the vision advantage for widescreen users.

You can use widescreen resolution on 4:3 monitor. It just adds black bars to top and bottom. It makes more sense to do this than to add black bars for widescreen users, since widescreens have been more popular for years now. So it's up to you whether to play with your native resolution and see a bit less (and no, it's not a huge advantage), or play with widescreen resolution and have black bars on top and bottom.

In mods like Hide and Seek its a HUGE advantage.

While running a Hide and Seek Server in 1.6 this error message occurs not always, but really often:

Code: [Select]

11-08-12 11:27:06 *Bad packet size (14): rp49 rs23
11-08-12 11:27:12 *Bad packet size (14): rp49 rs23
11-08-12 11:27:15 *Bad packet size (14): rp49 rs23
11-08-12 11:27:25 *Bad packet size (14): rp49 rs23
At this moment were noone ingame.

Code: [Select]

11-08-12 12:09:21 (1) Test killed (2) Omi with Barrett M82A1
11-08-12 12:09:24 *Bad packet size (14): rp49 rs23
11-08-12 12:09:26 *Bad packet size (14): rp49 rs23
but here were 2 players ingame

[Major xD]

That's quite the vision advantage for widescreen users.

You can use widescreen resolution on 4:3 monitor. It just adds black bars to top and bottom. It makes more sense to do this than to add black bars for widescreen users, since widescreens have been more popular for years now. So it's up to you whether to play with your native resolution and see a bit less (and no, it's not a huge advantage), or play with widescreen resolution and have black bars on top and bottom.

In mods like Hide and Seek its a HUGE advantage.

While running a Hide and Seek Server in 1.6 this error message occurs not always, but really often:

Code: [Select]

11-08-12 11:27:06 *Bad packet size (14): rp49 rs23
11-08-12 11:27:12 *Bad packet size (14): rp49 rs23
11-08-12 11:27:15 *Bad packet size (14): rp49 rs23
11-08-12 11:27:25 *Bad packet size (14): rp49 rs23
At this moment were noone ingame.

Code: [Select]

11-08-12 12:09:21 (1) Test killed (2) Omi with Barrett M82A1
11-08-12 12:09:24 *Bad packet size (14): rp49 rs23
11-08-12 12:09:26 *Bad packet size (14): rp49 rs23
but here were 2 players ingame

I think it happens when someone is trying to access your server with another version of the game...

-----


(10:11:10) 

• [Error] LogInSystem -> (OnAdminConnect): Unknown procedure

(10:11:10) 

• [Error] Nextmap Voter -> (OnAdminConnect): Unknown procedure

(10:11:10) 

• [Error] ServerVisits -> (OnAdminConnect): Unknown procedure

(10:11:11) 

• [Error] LogInSystem -> (OnAdminMessage): Unknown procedure

(10:11:11) 

• [Error] Nextmap Voter -> (OnAdminMessage): Unknown procedure

(10:11:11) 

• [Error] ServerVisits -> (OnAdminMessage): Unknown procedure

(10:11:11) 

• [Error] Nextmap Voter -> (OnCommand): Unknown procedure

(10:11:11) 

• [Error] ServerVisits -> (OnCommand): Unknown procedure

Why? =[

[KEEN]

trying...

gj guys, finally a rc for 1.6

[-Vis-]

That's quite the vision advantage for widescreen users.

You can use widescreen resolution on 4:3 monitor. It just adds black bars to top and bottom. It makes more sense to do this than to add black bars for widescreen users, since widescreens have been more popular for years now. So it's up to you whether to play with your native resolution and see a bit less (and no, it's not a huge advantage), or play with widescreen resolution and have black bars on top and bottom.

Yes, it's fair enough that everyone can use it, and I understand the reasons for it. I'm just a little miffed that I'm basically being forced to stray from my beloved 640x480 stretched window mode, because a 33% increase in horizontal vision (4:3 compared to 16:9) IS a substantial advantage, and I'd be a complete fool to not use it. I'll just have to get used to it, I guess.

Another thing, I'm trying to use a windowed resolution of 800x450 (16:9 ratio), but when I reloaded the config after running the game, I find that the resolution has been changed to 853x480. If I use 1600x900, however, it remains unchanged. It's not a big deal, just curious as to why that would happen.

[Monsteri]

*giggles*

[DorkeyDear]

Glad to see this. Can't read changelog right this moment, but looking forward to downloading this; just in time for the weekend

[Adek]

The old scoreboard order players by caps, not kills. Shouldn't it be contrarywise?

[Naliz]

Today is a good day to live in a good day my friend

[KEEN]

The old scoreboard order players by caps, not kills. Shouldn't it be contrarywise?

in dm yes, but in ctf I think that it's correct
and isn't old, in 1.5.1 order by kills

From: August 12, 2011, 01:21:35 pmalso, u can change that:

Added OldScoreBoard option in soldat.ini which can be used to render the scoreboard like it was before 1.5.1

[darDar]

gj, looking forward to test it soon. 

[Adek]

The old scoreboard order players by caps, not kills. Shouldn't it be contrarywise?

in dm yes, but in ctf I think that it's correct
and isn't old, in 1.5.1 order by kills

From: August 12, 2011, 01:21:35 pmalso, u can change that:

Added OldScoreBoard option in soldat.ini which can be used to render the scoreboard like it was before 1.5.1

Well in 1.5 and older versions it was ordering by kills even in ctf. I think the old scoreboard should stay as it was before so it ought to order by kills not caps like it is in the new one.

[Blacksheepboy]

Wow, stunning! I laughed when reading some of the bugs fixes

[12th_account]

* Mouse buttons 3 and 4s' mappings (and presumably up to and including button 8) are overwritten in soldat.ini with the default key mappings when Soldat is started.
* After assigning mouse button 4 to a key, it will assign itself to every subsequent attempted key change.
* The intro demo isn't compatible with 1.6.
* weapons.ini describes changes between 1.5 and 1.5.1. Should now be 1.5->1.6.
* Updated weapon changes omitted from changelog.
* Only radio buttons for 4:3 and 16:10 resolutions are present. No option for 16:9 resolutions. The amount of available room makes me think the component just isn't shown (http://skoskav.org/etc/soldat/etc/soldat160rc1-no16by9.png).
* Config (pictured above) claims to be 1.5.1.
* Registry key HKEY_CLASSES_ROOT\Soldat remains after uninstall.


Fantastic job by all developers. This version seems to be turning out great.

[CheeSeMan.]

sounds great only this wide screen resolution:

<tarrega> i nearly saw the enemy base fromthe respawn location on cobra

fix plz? unfair for others!

[Poop]

Good work devs. Alot of buzz on SCTFL forums after this announcement. I hope the release is near and I hope it will rejuvenate the scene.

My only concern is the aspect ratio, this should be an option in the server settings somehow, as its unfair to people who have small screens if people with larger screens can see further.

From: August 12, 2011, 06:16:07 pm

Good work devs. Alot of buzz on SCTFL forums after this announcement. I hope the release is near and I hope it will rejuvenate the scene.

My only concern is the aspect ratio, this should be an option in the server settings somehow, as its unfair to people who have small screens if people with larger screens can see further.

I just tested it out myself, yes this is a very large advantage IMO. I highly suggest this somehow be a server option that can be disabled as I don't see how this big of an advantage can be allowed in leagueplay.

[soulblade]

I am loving it to see all those bug fixes and not so many new 'features' *cough* Enesce low ping servers *cough*, very well done guys!!

Also ctf_Viet2 is a good effort, but trying to remake all maps was a bad idea - only unpopular maps should have been remade. Viet is one of the more popular maps in competitive Soldat, so it really needs to be kept in it's original form. The other remakes are fine as they were barely played ever in SCTFL.

From: August 12, 2011, 08:00:20 pm

The old scoreboard order players by caps, not kills. Shouldn't it be contrarywise?

in dm yes, but in ctf I think that it's correct
and isn't old, in 1.5.1 order by kills

From: August 12, 2011, 01:21:35 pmalso, u can change that:

Added OldScoreBoard option in soldat.ini which can be used to render the scoreboard like it was before 1.5.1

Well in 1.5 and older versions it was ordering by kills even in ctf. I think the old scoreboard should stay as it was before so it ought to order by kills not caps like it is in the new one.

It was ordered by points! 20 points for a cap. I think it would be best to keep that old system but with the scoreboard also showing how many caps each player has. At the end of the day it's ctf not dm, capping should be encouraged.

That's quite the vision advantage for widescreen users.

You can use widescreen resolution on 4:3 monitor. It just adds black bars to top and bottom. It makes more sense to do this than to add black bars for widescreen users, since widescreens have been more popular for years now. So it's up to you whether to play with your native resolution and see a bit less (and no, it's not a huge advantage), or play with widescreen resolution and have black bars on top and bottom.

Agreed

[Squakingcow]

Widescreen support could change soldat quite a bit, since it will have been designed from the outset so that you could only see a certain distance.

It will be interesting to see how the way people play the game changes, as it could potentially become harder to go unnoticed by your enemies and the engagement range will increase, which could potentially be harmful to short-range weapons such as the spas, m79 and MP5.

[Mr]

Thanks for the release - that indeed is a huge changelog, loving to see some of those very annoying bugs fixed.

I'm leaving you this in case you haven't seen it on your IRC channel:

<Mr>Shoozza: I have a weird bug here, was able to reproduce it on two machines however so I am certain it is a bug in Soldat. When I have not registered Soldat (no key in registry), the game crashes unless it is started as administrator (Windows 7 x64).
<Mr>I suspect that this is a bug in ASProtect
<Mr>It might also be that ASProtect does not cause this but displaying the "unregistered copy" message does (the blue window with the readme and ads)

[wojtex]

And whether it will lock on crasher servers are?
Excuse my English is terrible

[Adek]

It was ordered by points! 20 points for a cap. I think it would be best to keep that old system but with the scoreboard also showing how many caps each player has. At the end of the day it's ctf not dm, capping should be encouraged.

Yes, my bad, in older versions it was 20 points per cap. In 1.5 caps were separated from kills, but the player with more kills was higher than one with better cap score And here's my point - the old scoreboard IMO should stay as it was in 1.5

Besides that this version seems cool GJ by devs