Quick Questions

[Akinaro]

Ah, then I'm not sure what's causing your issues. I quickly tested ctf_Laos with a 2000x2000 texture in PW and Soldat, and it seemed to work. Maybe your GPU just dislikes non-binary sized textures? Try using textures that are in power-of-two, e.g. 1024x512, 2048x2048, and so on.

its not size problem... I write in in first question...

(...)but PW/Soldat have problems with png textures file even with 700x700(random errors in PW or weird bugs in Soldat).

i get random error, and after that PW crash or Soldat dont see this textures..

so what if its support it if Soldat and PW have huge problems with it? this error I get after selecting 1024x600 png file...
PS. I thing we should end this conversation here, because its against the rules of this topic.
after I check tga and jpg files I create new topic about it.

[Viral]

Will you unlock the maps without the "ctf_" prefix to be shown on the list in SP mode? Atm. you can't play them, even if they have flags and team spawns :C

[15th_account]

What's SP mode?

If you want to force certain maps to be played, I think you can edit maplist.txt in the Soldat folder, or mid-game run the command "/loadlist maplist.txt"

[Akinaro]

Single Player :] <lol>

[BKT]

Wow, I just noticed this... 

Why is it that bullet impact point seem to be at the end of the bullet graphic (or, maybe, the beginning of bullet trail?) instead of at the front like what we intuitively think how it should be? ... This would explains some of the weird "Why da fuq won't u just die!" moment I encountered online.

This doesn't seem to be something that happened recently and is always like this; made me curious of what the reason behind it. 

EDIT::

After a bit more  testing...

The impact point of bullets, at least the one with 21 pixel width, is not actually at the back as I previously said it is, but certainly isn't at the front either and is somewhere around the mid-point... And after more testing with a modified bullet graphic that have the bullet 'mass' moved further back for a varying distances, I think I can answer my own question now— since most of the bullet in this game is not a 'point' bullet but rather more like an arrow, so if the impact point of the bullet were to be at the front of the bullet without any headroom, the bullet will seem to disappear rather abruptly and lack the 'the bullet has penetrated and sunk into the target' feels to it, and occasionally may even seem to disappear before it actually hit at some angle of impact and this is probably due to the limitation of the game graphic engine and hence necessitate some headroom in the bullet graphic as a safeguard against this.

[darDar]

I think MM tested that with real weapons and he obviously found out that the real damage takes affect when the bullet goes through your body and not when getting in first contact with it.

Enough trolling from my side for the next 4 years

[CheeSeMan.]

Whens the next dev log?

[15th_account]

Oh yeah, devlogs. I blame nice weather and Mario Kart 8 for the lack of major progress. :d

I'll have a lot more spare time the coming weeks though, so hopefully the devlogs will be more frequent again.


BKT: I don't really know. The player collision check basically draws a straight line between where the bullet currently is and where it would be in the next frame, and checks for any collisions. The bullet rendering is probably the main source of deceitful representation though as it has to account for texture size, bullet speed and lag... and it's mostly coded by MM so it's guaranteed to be glitchy.

[BKT]

I think MM tested that with real weapons and he obviously found out that the real damage takes affect when the bullet goes through your body and not when getting in first contact with it.

Enough trolling from my side for the next 4 years

Oh you... 

BKT: I don't really know. The player collision check basically draws a straight line between where the bullet currently is and where it would be in the next frame, and checks for any collisions. The bullet rendering is probably the main source of deceitful representation though as it has to account for texture size, bullet speed and lag... and it's mostly coded by MM so it's guaranteed to be glitchy.

Thanks for your input; any insight into how the hit detection work is always appreciated. 

BTW, could you enlighten me on how bullet able to register (i.e. hit people) through obstacle in some situation (from above, your shot can hit people who jetting right beneath the bridge in DM_Jungle, for instance) ... ? 

[15th_account]

Well that bridge does have three places where bullets can pass through. It's probably that.

[BKT]

Well, more like this (Ruger vs Boogieman) :

[BKT]

::Double post:: 


There are some pub servers that, whenever I ping it from either the in-game lobby or from pinging it outside of the game, I got a relatively high ping, but when I actually join in the game, my ping (as shown in the scoreboard/alt+F3) became significantly lower* somehow... Yet, it doesn't felt at all like I actually played with the lower ping but more like I still playing with the higher ping...

Anyone feels like explaining to me what's going on? 



* I'm talking about ~40-50 lower ping here, so this certainly is not about the usual "Soldat use/shows a bogus ping instead of a real one" issue here...

[Shoozza]

Soldat server ping is... weird. I the server can fake ingame pings (don't ask) it could be that the pings are not the same for some reason (or someone fakes ingame ping - but that's a rare case) so if you have details on the exact ping you get outside and ingame add some info to the bugtracker (or create a new bugreport if its not there already)

[BKT]

The server in question is "! #Soldat2D.ru Pub DM" server:

Using ping tool:

Code: [Select]

Pinging [88.151.116.65] with 32 bytes ->bytes=32 time=303ms TTL=51
Pinging [88.151.116.65] with 32 bytes ->bytes=32 time=300ms TTL=51
Pinging [88.151.116.65] with 32 bytes ->bytes=32 time=301ms TTL=51
Pinging [88.151.116.65] with 32 bytes ->bytes=32 time=302ms TTL=51
Pinging [88.151.116.65] with 32 bytes ->bytes=32 time=299ms TTL=51
In-game lobby: 297-313 ms

As shown once joined the game: 250-266 ms

One of the most noticeable weird thing on this server is that the respawn countdown timer consistently act in a strange way; it kept 'rollback' the clock as if the game try to compensate for the bogus lower ping or something.

Kinda like this (-0.1 second per interval) :—

3.0
2.9
2.8
2.7
2.8
2.7
2.6
2.5
2.4
2.3
2.4
2.3
2.2
2.2
2.1
2.0
... and so fort until 0.0

AFAIK no other server I've played thus far had this sort of behavior.

[Drax]

Will you make new HD Icon.exe for soldat 1.7.0

you could cut out the guy from this picture and make something good out of it. 



Any new weapons for soldat 1.7.0 like bow or crossbow to primary list

if you guys have already answered these questions somewhere I am sorry for asking again...

[Shoozza]

Maybe someone will make a HD icon for 1.7.0, but it is not high priority.

There will be no new weapons for 1.7.0. Nobody is working on that and it isn't planned.

[Drax]

@Shoozza sorry for making it a discussion but what if I would work on new weapons? Come on!
For soo many years soldat didn't get new weapons!

I have already done some good work on making 2 new weapons!
here: http://forums.soldat.pl/index.php?topic=44064.0

[Shoozza]

Sorry but I cannot even balance the current weapons atm.
I appreciate your work on the new weapons but it is pretty low on our list.
There is a lot to do before we can think about it.

[Drax]

How about you guys add "In-game cursor changer"? It would be an option next to interface changer in game, but except for name it would also display little icon of chosen cursor. I suggest to make a separate folder for cursors. I could make such folder with many different cursors.

how do you like that Shoozza ??

[Shoozza]

I'd like to avoid too much options so no not atm. Maybe in the future but honestly just create a mod with a different cursor and all the same graphics and you have your switcher.