Print

Liero v1.0 – 100lt
IP: 91.156.42.210
Game Mode: Death Match
Lives: 5
Max Kills: 20
Version: OpenLieroX 0.58 rc3

Players:

Cruel v0.96 – 50lt
IP: 69.255.183.244
Game Mode: Death Match
Lives: 5
Max Kills: 0
Version: OpenLieroX 0.58 rc3

Players:
iRod(0 lives, 0 kills)
[CPU]I'm Not A Human(5 lives, 0 kills)
[CPU]I'm Not A Human(5 lives, 0 kills)

Modern Warfare1.0 – 20lt
IP: 37.205.11.54
Game Mode: Death Match
Lives: 7
Max Kills: 23
Version: OpenLieroX 0.58 rc3

Players:

[SorZ]

Then again some want only 0.56 settings some want minor things from OLX and that's where this idea fails a bit.

Well those things that are listed so far, sure is not taking much space.
And they are not affecting gameplay very much either.
I see it rather as usefull options.

After all these things listed isn't something very drastic, like an option like strafe would be for example.

[Midnight]

Yes, these options seem pretty reasonable. How about making this like a game profile - you can choose "LX mode" and "OLX mode" and it would change all the settings (including shown GUI options, hosting settings etc.).

Impressive idea and it would help to "connect older players with newer ones". Cool!

[*Gyogyi*]

Albert, As long as you can ban these betea releases Im not against letting other people to download them!

But until now at least, you didnt use anything to bann these versions if needed.

Why SorZs suggestion is good if only 3 of us have tested it is the most common problem, that older version users cant save themself against these versions.

If the stuff works well, we would of course tell you that you are able to upload it and let everyone to test it.

These suggestions are good, howerver I will send you the beta 2 I have, and after youve taken a look on it, that's features should be enabled for the default LX56 filter.



PS: Whoa, Albert, you got my 888th Post, this should mean something....... POSITIVE

[joni]

What about wallshots?
I've noticed that in .56 bullets go easier through walls than they do in OLXs.

[Nets]

Olx LX56PhysicsFPS=84
LX56 LX56PhysicsFPS=max

isnt this the answer?

[albert]

Ok, I have implemented these now:
- LX56PhysicsFPS
- ForceSameLX56PhysicsFPS
- NinjaropePrecision
- ForceLX56Aim

NinjaropePrecision is another thing I haven't mentioned yet. While comparing the original LX56 code to the current OLX code, I figured out that even with modifying the FPS, the ninjarope still had some extension to LX56 which made it more exact (no matter how low the FPS is).

NinjaropePrecision=0 completely disables this extra precision and thus ninjarope precision is completely FPS depedent and exactly like LX56. NinjaropePrecision=1 is kind of what you have since 0.57 beta4 (and all further versions, including the latest 0.58 and latest 0.59).

I don't have time right now to make a release (and I also want to have some more stuff finished for the next release) but you can try out by compiling it yourself from the current Git code.

SorZ, as you have MacOSX, compiling is not really that complicated. For Linux users here, it is much more trivial though. For Windows, it's a bit more complicated but I have updated the dev package on SF so it should be much more easy now than it was before if you use MSVC2010.

[Cizin]

Wow, this thing really happening?!?!?

I'm moving to Olx i  guess.

Cheers albert.



Safe.

[Roxxy~]

If you can get Olx looking like 0.56, i'm chainging right away.

Great doing Albert.

[SorZ]

Ok, I have implemented these now:
- LX56PhysicsFPS
- ForceSameLX56PhysicsFPS
- NinjaropePrecision
- ForceLX56Aim

NinjaropePrecision is another thing I haven't mentioned yet. While comparing the original LX56 code to the current OLX code, I figured out that even with modifying the FPS, the ninjarope still had some extension to LX56 which made it more exact (no matter how low the FPS is).

NinjaropePrecision=0 completely disables this extra precision and thus ninjarope precision is completely FPS depedent and exactly like LX56. NinjaropePrecision=1 is kind of what you have since 0.57 beta4 (and all further versions, including the latest 0.58 and latest 0.59).

I don't have time right now to make a release (and I also want to have some more stuff finished for the next release) but you can try out by compiling it yourself from the current Git code.

SorZ, as you have MacOSX, compiling is not really that complicated. For Linux users here, it is much more trivial though. For Windows, it's a bit more complicated but I have updated the dev package on SF so it should be much more easy now than it was before if you use MSVC2010.

Sounds good to me!

By the way, if there's some kind of tutorial how to compile.
And if I get all codes/files needed I think I can manage to do it.

[albert]

By the way, if there's some kind of tutorial how to compile.
And if I get all codes/files needed I think I can manage to do it.

http://www.openlierox.net/wiki/index.php/Compile_OpenLieroX

[MiLeC]

Ok, I have implemented these now:
- LX56PhysicsFPS
- ForceSameLX56PhysicsFPS
- NinjaropePrecision
- ForceLX56Aim

NinjaropePrecision is another thing I haven't mentioned yet. While comparing the original LX56 code to the current OLX code, I figured out that even with modifying the FPS, the ninjarope still had some extension to LX56 which made it more exact (no matter how low the FPS is).

NinjaropePrecision=0 completely disables this extra precision and thus ninjarope precision is completely FPS depedent and exactly like LX56. NinjaropePrecision=1 is kind of what you have since 0.57 beta4 (and all further versions, including the latest 0.58 and latest 0.59).

I don't have time right now to make a release (and I also want to have some more stuff finished for the next release) but you can try out by compiling it yourself from the current Git code.

SorZ, as you have MacOSX, compiling is not really that complicated. For Linux users here, it is much more trivial though. For Windows, it's a bit more complicated but I have updated the dev package on SF so it should be much more easy now than it was before if you use MSVC2010.

"ShowOnlyLX56SettingsServers

This could be more generalised to any kind of serverlist filter. Like if you want to filter out only CTF servers or only DM servers or only Liero v1.0 servers or whatever."

Hope you won't forget this one. I consider this one of most important and brilliant change for ages.

Mayby different versions in same game could work together like this. Not sure how complicated it will be for new users to understand LX genre, if theres different versions of actual game included in same server list..

But atleast this would serve oldskoolers..

So mayby make release also this included. Or mayby it already was and I just didn't understand..

Then one suggestion to make it easier to understand for new comers.

In options there could be some info about the game.. (NOBODY PROLLY EVER READS ANY INFOS....)

LX 0,56: Original version of Liero extreme wich most of the oldskoolers likes.

OLX: Ongoing project to develope game further on. Many player's likes to use this because it has many new features and settings, but as said its under development. Due limited resources OLX is developed alongside the LX 0,56 to get more feedback and players testing it. But it's possible to set wich versions of the game you will be able to see..

Something like that...

[albert]

No I don't have forgotten that and will not forget about these things. (Whereby the only things missing from my suggested options are ShowOnlyLX56Stuff and ShowOnlyLX56SettingsServers, all others are finished.)

It's just that these are more complicated. ShowOnlyLX56Stuff would mostly be a work-in-progress. A first simple version could strip out most of the stuff, to make it more clean though will require more work.

ShowOnlyLX56SettingsServers is the most complicated as it requires most work to do. I already put some hours of work into some preparation of this today but I didn't even started to implement the thing itself (most work I did today was to prepare our server list handling and to clean old and ugly code up to allow sth like that - and that was already quite a lot of work).

I am kind of limited in time though right now, so I cannot really invest more time for the next weeks into this. I'm thinking now if I should make still a release in the current state with those stuff not yet implemented (after doing some other slight cleanup here and there) or if I should just wait.

[RussG]

Why rush? I'd say wait a little. 

[Rakkula]

ForceLX56AimThis would force all players on your server to have the LX56 aimspeed settings.

I agree with the rest of the options you've been planning but this option seriously sucks ass deep and hard.
Wanna know why?
This is why:

That's exactly the part where it fails Sak.
LX aimspeed can't really be compared to FPS mouse sensitivity, at least if we look in "pros-cons" perspective.

But still the thing is, if the setting is server-sided, there is no problem. And even if it isn't, there's only a small problem.

I think you're wrong. It's a huge problem. Aim being server-sided practically means hosts set aim speed the way they like.
      Imagine switching  between servers, every server using its own aim speed: how the hell are you supposed to aim with ever switching aim speed? If aim was server-sided, I would only host and not join anyone else's server. But shit... why would anyone join my server if it uses different aim from what they're used to? ****. I guess that would totally ruin the game.

In other words, having to play with aim you're not used to ruins the game. Don't do this, albert. Period.

[Tafka]

I don't think it's good either to force others for something, but I don't think any players would go that ****y in their servers to force others some radically different aim speed.

[*Gyogyi*]

I agree on Tafkas opinion, This option should exsist  to force those people, who brag with their "advantage" if it happens. then its just like a forum Staff's  moderation right.

[Rakkula]

[Griffin]

In other words, having to play with aim you're not used to ruins the game. Don't do this, albert. Period.

He's right, you should never have to relearn your controls when entering a server. For this reason strafe should also be allowed everywhere and any other worm modifying things.
The only things that really make sense to vary (off the top of my head) are the physics as implemented by mods and friction for surfaces in levels (someday that should be added).

[albert]

ForceLX56Aim, as the name suggests, enforces the aim to be like LX56. So any custom settings of the server or the client are ignored, it will just be like LX56 for everyone.

I thought that makes more sense than an option like ForceSameAimAsServer or so.

So, when you enter any server and you have non-LX56-like aim settings, you have the two possible cases: Either you have your own non-LX56-like aim settings or you have the LX56 aim settings. In case you have anyway the LX56 aim settings yourself (as most oldschoolers probably have anyway), you will never see any different aim settings on any server.

For those with custom non-LX56 aim settings, who really don't want to go on a server which forces LX56 aim: The server list filter can hide such servers away from you.

[joni]

Well, forceaim could be optional setting.
So if the host want's to people use 56 aim, they will be forced and told about it.

Otherwise, it's not so good idea.