| the_map | Zehra: think F7 does that | 00:01 |
|---|---|---|
| the_map | not sure about on rabbit hunt specifically, but multiple hunts are possible | 00:02 |
| Zehra | the_map: I believe you misunderstood what I said.... For instance on rabbit chase mode specifically.... | 00:02 |
| blast007 | rabbit chase might tap into the hunt system instead of doing it's own thing | 00:02 |
| Zehra | If there is a new "rabbit" selected, all additional or other players "hunted" will simply be "removed" from "hunt". | 00:03 |
| Zehra | is selected* | 00:03 |
| Zehra | The sole player being hunted, will now be the rabbit. | 00:04 |
| Zehra | Since the client actions would vary if a change would be introduced in the current protocol, I assume this would only be suitable within a protocol break. | 00:05 |
| *** PamelaAlexa <PamelaAlexa!a37dfb7d@gateway/web/cgi-irc/kiwiirc.com/ip.163.125.251.125> has joined #bzflag | 00:27 | |
| *** PamelaAlexa <PamelaAlexa!a37dfb7d@gateway/web/cgi-irc/kiwiirc.com/ip.163.125.251.125> has quit IRC (Client Quit) | 00:30 | |
| Zehra | Seems grabbing flags and dying may possibly lead to odd issues in game client. | 02:01 |
| Zehra | Client HUD "rotates" counterclockwise in spinning motion. Awaiting for respawn does not lead to it occurring. | 02:02 |
| allejo | huh | 02:23 |
| blast007 | Zehra: by "HUD" what do you mean? | 02:25 |
| Zehra | blast007: The 3D view and radar. | 02:26 |
| blast007 | well those are two different things | 02:26 |
| blast007 | the HUD is not the 3D view | 02:26 |
| blast007 | HUD = Heads Up Display. It's the overlay over the 3D view. | 02:27 |
| blast007 | https://en.wikipedia.org/wiki/Head-up_display | 02:27 |
| blast007 | so you're just saying that your camera spins around while dead? | 02:28 |
| Zehra | Yes. | 02:29 |
| blast007 | how do we reproduce it? | 02:29 |
| blast007 | cuz like, "grabbing flags and dying" isn't really descriptive | 02:29 |
| Zehra | I'm unsure, but the last things which happened were the tank falling, landing on a flag and getting shot with laser, also possibly jump "triggered" to jump upon landing. | 02:31 |
| Zehra | Just kind of putting it out there, someone else might have seen something similar happen, so increased possibility of finding bug. | 02:31 |
| allejo | ah yes, another tragic victim of gravity | 02:36 |
| BZNotify | 2.4 @ bzflag: allejo pushed 1 commit (https://git.io/JfqIx): | 03:29 |
| BZNotify | 2.4 @ bzflag: allejo 138179: Fix Changelog entry of nonexistent API event (https://git.io/JfqIp) | 03:29 |
| allejo | my bad | 03:29 |
| *** Zehra <Zehra!~Zehra@unaffiliated/zehra> has quit IRC (Quit: Gone for now.) | 03:38 | |
| BZNotify | master @ bzflag.org: allejo pushed 2 commits (https://git.io/Jfqtt): | 04:35 |
| BZNotify | master @ bzflag.org: allejo afa0ec: Add support for extending API event docs (https://git.io/Jfqtq) | 04:35 |
| BZNotify | master @ bzflag.org: allejo cf0132: Document bz_ePlayerDeathFinalizedEvent (https://git.io/Jfqtm) | 04:35 |
| allejo | aww... zehra left before he could see those glorious pushes to document an event that is only slightly different | 04:39 |
| The_Noah | When I start BZFlag (2.4.20) it's stuck on a black screen then goes Not Responding. It was working fine yesterday, and I think I had the issue with 2.4.18 once as well. | 04:45 |
| BZNotify | master @ bzflag.org: allejo pushed 1 commit (https://git.io/JfqtC): | 04:53 |
| BZNotify | master @ bzflag.org: allejo 20de10: Remove erroneous changelong entry (https://git.io/JfqtW) | 04:53 |
| *** tupone <tupone!~alfredo@gentoo/developer/tupone> has quit IRC (Ping timeout: 265 seconds) | 05:20 | |
| *** tupone <tupone!~alfredo@gentoo/developer/tupone> has joined #bzflag | 05:21 | |
| *** bier <bier!~bier@helixnetworks.de> has quit IRC (Ping timeout: 256 seconds) | 05:58 | |
| *** bier <bier!~bier@helixnetworks.de> has joined #bzflag | 07:33 | |
| *** nOob_ <nOob_!54e8f783@84.232.247.131> has joined #bzflag | 09:19 | |
| *** nOob_ <nOob_!54e8f783@84.232.247.131> has left #bzflag | 09:20 | |
| *** User49 <User49!~FieldSobe@unaffiliated/user49> has joined #bzflag | 09:58 | |
| *** FieldSobers <FieldSobers!~FieldSobe@unaffiliated/user49> has quit IRC (Ping timeout: 260 seconds) | 10:01 | |
| blast007 | The_Noah: check the contents of your config file. Is there anything strange with it? | 11:07 |
| BZNotify | 2.4 @ bzflag: blast007 pushed 1 commit (https://git.io/Jfq8D): | 11:45 |
| BZNotify | 2.4 @ bzflag: blast007 c3d232: Bump version to 2.4.21. (https://git.io/Jfq8y) | 11:45 |
| blast007 | The_Noah: and if you do find the config file is the problem, could you send it to me? I've never been able to reproduce a bad config file, but it has happened to enough people that I'd like to figure out what config file content makes the game break. | 11:47 |
| blast007 | as for Zehra's issue, without looking at the code, my guess is that there's some out-of-order handling that caused the jump to be registered after the death, which updated the local tank's state to something else (like InAir) instead of Exploding | 14:37 |
| blast007 | hmm, though I guess InAir is a location, not the state. So maybe it's having the 'Falling' state mixed with 'Exploding', or just 'Falling' by itself (so, Dead + Falling). | 14:43 |
| The_Noah | In the config what is `startcode` ? | 16:23 |
| *** tupone <tupone!~alfredo@gentoo/developer/tupone> has quit IRC (*.net *.split) | 16:26 | |
| *** brlcad <brlcad!~sean@104.225.5.10> has quit IRC (*.net *.split) | 16:26 | |
| *** tupone <tupone!~alfredo@gentoo/developer/tupone> has joined #bzflag | 16:31 | |
| *** brlcad <brlcad!~sean@104.225.5.10> has joined #bzflag | 16:32 | |
| *** ChanServ <ChanServ!ChanServ@services.> has quit IRC (*.net *.split) | 16:42 | |
| *** ChanServ <ChanServ!ChanServ@services.> has joined #bzflag | 16:45 | |
| *** hitchcock.freenode.net sets mode: +o ChanServ | 16:45 | |
| *** brlcad <brlcad!~sean@104.225.5.10> has quit IRC (*.net *.split) | 17:26 | |
| *** tupone <tupone!~alfredo@gentoo/developer/tupone> has quit IRC (*.net *.split) | 17:26 | |
| *** brlcad <brlcad!~sean@104.225.5.10> has joined #bzflag | 17:29 | |
| *** tupone <tupone!~alfredo@gentoo/developer/tupone> has joined #bzflag | 17:29 | |
| blast007 | The_Noah: startcode is an encode string for the Start Server settings | 17:32 |
| The_Noah | Ah. | 17:32 |
| The_Noah | I deleted my config file, but it still has the same issue. I also deleted the cache folder and still broken. Would you like me to still send you my config? | 17:32 |
| blast007 | nah, if it's failing without a config, then it isn't a config issue | 17:34 |
| blast007 | is it only with 2.4.20? | 17:34 |
| The_Noah | I had the issue once recently with 2.4.18, but I believe it went away by itself. Should I install an older version to see if it has the issue as well? | 17:35 |
| blast007 | yeah, if you want to | 17:35 |
| blast007 | just want to make sure it's not something with the new release :) | 17:36 |
| The_Noah | Okay. | 17:36 |
| The_Noah | I have the issue with 2.4.10 and 2.4.18 as well. | 17:39 |
| *** ChanServ <ChanServ!ChanServ@services.> has quit IRC (*.net *.split) | 17:39 | |
| *** ChanServ <ChanServ!ChanServ@services.> has joined #bzflag | 17:42 | |
| *** hitchcock.freenode.net sets mode: +o ChanServ | 17:42 | |
| blast007 | The_Noah: what video card / driver do you have? | 17:55 |
| blast007 | (and it is a hybrid system with two GPUs?) | 17:56 |
| The_Noah | I have a nVidia GTX 1050 Ti, single card. | 17:57 |
| blast007 | latest driver? | 18:22 |
| The_Noah | No, I have 442.74. | 18:55 |
| *** disco- <disco-!~disco@unaffiliated/disco-> has quit IRC (Ping timeout: 258 seconds) | 21:26 | |
| *** disco- <disco-!~disco@unaffiliated/disco-> has joined #bzflag | 22:03 | |
Generated by irclog2html.py 2.17.3.dev0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!