Official forums for BZFlag.org

I tried to test this, but there are a few issues: - I can't run it multiple times on the same machine, as the first instance grabs the mouse even when it doesn't have focus. - There is no way I found to run a server (without gui) from the command line. A public server should be hosted so players can...

Ok, I'll bite. I think to make the game attractive it obviously needs to get new features and to fix the decades old problems. And for it to happen 1-The barrier to entry for contributors has to be lowered quite a bit, and 2- The game should be developed by people who actually play it, occasionally ...

ccb, I have concluded that the change to game play introduced by altering bullets speed would throw many LU players off. Perhaps if it is a new game, or as you said, on other maps, this might fit better. IMO, that leaves us with the only other mean to improve the situation, that is showing the lag s...

I consider this suggestion rejected. Thanks for your time.

Actually we are used to a lot of variation, since tank velocity is added when determining shot speed. If my understanding is correct, a tank moves forward at 25 world units/sec, and backward at 12.5 wu/sec which means the slowest shot is 87.5 wu/sec and the fastest is 125 wu/sec . For this mod to ha...

The tank indicator would be visible on the radar. I do not see why it would be hard to identify the source of bullets in this case. Perhaps in a situation where there are 4 or more attacking tanks this would be an issue, but this is a rare situation.

There are two possibilities
- Mark tank differently based on its current lag. The result is that bullet speed from the same tank can vary if there is a lag spike
- Fix the bullet speed for every tank based on long term average lag, ignoring any in-game lag variation

Exuro, yes, this is how it works. In reality the variation is not too great, as it fluctuates between 0% for very low lg and around 8% for very high lag (500ms combined)

blast, I have read the documents you shared, but I have not found any thing that change my mind on the subject. The methods applied in these cases if taken to BZFlag will lead to either or both of: 1- Jerky movement on the client, as the server will often disagree with the client and the client has ...

I meant that death calc should continue to be done based on client side detection, having it any other way will adversely affect enjoyment of the game. BTW, I think that bullet speed increase is not very different from spawning a bullet in a more advanced position, the only difference being that in ...

Constitution Consider we have players A,B and C , and they lag 100, 200, 300 respectively. When player A shoots, player B will see the bullet moving at 1.1 times normal speed, and player C will see it moving at 1.2 times normal speed. It does not depend on the position of any player, but only their ...

The lag compensation method used in other games which you have described will not work for bzflag. And I think this is something all active players can agree on. Rewarding based on latency is rewarding players for where they are located, which I think is not the way to go. The solution should improv...

Hi, I have brought up the issue of handling lag before and suggested two ways to improve it. I am again bringing the issue up for more discussion, and suggesting a new solution. It is a three component solution, two of which are known since I made them before, and even created POC implementations fo...

The good
1- Open source.
2- Simple play yet very challenging against good players (GU/DUC specific.)

The bad
1- No mechanism to get a quick match going.
2- The graphics can get improved, while remaining simple.

Logitech g700 5700 dpi and I play @900 dpi.

Would also add that I use acceleration of 1.42 and 0 pixel acc threshold.

Created an in-game video to show it in action - https://vid.me/Lm8c
Emulated lag on two clients to show where bullets would appear over time on both.
Notice how the bullets hit the block nearly simultaneously although the initial shot event is delayed by over 1.5 sec on the 2nd client.

There is a server up temporarily to test this functionality @ 192.241.121.197:5154 (titled: Public Hix - Lag Compensation)

A few players have tested it and the reception has been generally positive

Please do test it while the server is up. I will keep it running for a short time.

It is intended to be as simple to implement as possible, but with reasonable gain. The amount a tank can move in <500 ms is not as significant as the amount a bullet moves in the same period, so I opted to neglect it. I think the bullet is the only element that moves predictably, players can get use...

http://jsfiddle.net/2kfnxLnz/ The link above is demonstration of the idea. If you look at it, the orange bullet is what the shooter sees, blue one is what the dodging player would see, while the purple one is speed adjusted to compensate for the lag. I think this is a reasonable compromise for a few...

This is another training map that works in solo mode. Try it, send your opinions. The server should be started locally using a command like- bzfs -ms 3 -j +r -world cages.bzw _And_ the client should be started with a command such as- bzflag -solo 8 -team rogue mycallsign@127.0.0.1:5154 bzfi0004.jpg ...

I was toying with the world weapon object and made some maps that deploy it for single player practice. I will post these maps in one thread since they share the same theme. The first one is for corner rico dodging practice. Invisible enemies keep shooting ricochet sprays in 2s or 3s randomly within...

There is very little to show at this point to warrant a screenshot, but I posted it since someone showed interest in game chat . I intend to expand on the concept of automated shooters to make a map for dodging practice.

blast wrote:You need to specify a license that this map is released under.

Done.

Here is a very simple map for the solo player. I used a helper script to generate it which I also wrote in Ruby, ask if interested.

License: Creative Commons Attribution-Share Alike 3.0

PS: I didnt see the "work in progress" section before posting, which I think would be more fitting for this post.

So I made one more change. rather than blinking the tank as if hunted, just draw a circle around each tank that would represent the area the tank possibly is by adding local and remote lags and giving the circle a radius of the max distance the tank can move in this period. I find this to be very us...