| 11:51.13 | *** join/#bzflag infobot (ibot@rikers.org) |
| 11:51.13 | *** topic/#bzflag is https://BZFlag.org || http://ohloh.net/p/bzflag || https://bzflag.org/help || Channel Logs: http://infobot.rikers.org/%23bzflag/ || 2.4.12 released! https://forums.bzflag.org/viewtopic.php?f=62&t=19720 |
| 11:51.13 | *** mode/#bzflag [+v infobot] by ChanServ |
| 12:22.14 | *** join/#bzflag spldart (~spldart@bzflag/contributor/spldart) |
| 12:22.14 | *** mode/#bzflag [+v spldart] by ChanServ |
| 12:23.27 | spldart | My latest build of bzflag decided to span my 20 and 40 inch monitor. How can I stop that? |
| 12:38.14 | blast007 | your system is probably telling BZFlag that you just have one (very wide) screen |
| 12:38.33 | blast007 | so you'd have to change how your system reports that |
| 12:41.38 | spldart | well poop |
| 12:43.17 | spldart | in settings it does see x2 monitor and shows the different resolution and dimention. Anyone have an idea where in debian 9 i might find this misreporting setting? *me pokes around his settings some more.* |
| 12:44.38 | spldart | Wait... see something. report back later. gotta try something |
| 12:57.16 | spldart | welp... fail |
| 13:01.53 | *** join/#bzflag spldart (~spldart@bzflag/contributor/spldart) |
| 13:01.54 | *** mode/#bzflag [+v spldart] by ChanServ |
| 13:03.05 | spldart | Oh wow. BZ client got real pissy when I tried windowed and everything hard crashed. Dunno what changed after my last git pull but Da... I mean poop! |
| 13:04.46 | blast007 | "everything hard crashed" meaning what, exactly? |
| 13:05.12 | Delusional | would a map zone that prohibits shooting be possible? |
| 13:05.35 | spldart | screens went black, short delay, back to login screen, re logged in but all my other applications were gone, didn't see them in top either. |
| 13:05.49 | blast007 | spldart: that's not a bz thing then, that's your system misbehaving |
| 13:06.21 | spldart | Then it's only misbehaving with my latest build of you know what ;~p |
| 13:07.08 | blast007 | most likely it would behave the same way with the older build |
| 13:07.18 | spldart | k |
| 13:07.59 | spldart | I'll dink with it some more later. Thanks for the input. |
| 13:08.31 | *** mode/#bzflag [-v short_circuit] by ChanServ |
| 18:35.09 | tupone | short_circuit: have you tried with git bisect ? |
| 19:06.04 | blast007 | tupone: if xorg is crashing, it shouldn't be anything we changed |
| 19:19.30 | *** join/#bzflag zuii (~cauchy@BC9C5B1F.mobile.pool.telekom.hu) |
| 19:27.11 | tupone | I understand, but if he is sure ... |
| 19:28.28 | tupone | blast007: you know who has made that MINGW ifdef ? |
| 19:29.19 | tupone | maybe in sourceforge there is the history |
| 19:29.41 | blast007 | https://github.com/BZFlag-Dev/bzflag/commit/ca81a5573f4e85052561125ffa37cfae714fc99c |
| 19:30.38 | blast007 | the entire SVN history was migrated to git/github |
| 19:32.23 | tupone | ahh ok. when we go to 2.6 I would like to set everything as MINGW (at least for SceneNode). The profile say we gain 2% there on my scenario (a lot of flags) |
| 19:33.27 | blast007 | I don't know what that means |
| 19:34.34 | blast007 | we should just remove any special tweaks to make cygwin and mingw32 work |
| 19:34.53 | blast007 | Visual Studio is free, unlike it was back in 2003 |
| 19:36.26 | tupone | The thing is that instead of callong glColor4 we call myColor4 to override the color in some special case. when not MINGW we use a dispatching call, while on mingw is just and if (colorOverride) IIUC |
| 19:37.09 | tupone | I think the MINGW things is better |
| 20:13.18 | short_circuit | googling bisect now. May try that later. I'd love a shortcut to get a 3 month old checkout just to make sure it's not one of my updates that caused this. |
| 20:17.03 | blast007 | just build 2.4.12 and see if that does the same thing |
| 20:17.08 | blast007 | (that's from October) |
| 20:19.02 | short_circuit | I'll try that later. That will decisively find my problem ;) |
| 20:23.53 | *** join/#bzflag Zehra (~Zehra@unaffiliated/zehra) |
| 20:44.43 | *** join/#bzflag AAA_awright (~aaa@ns4001783.ip-198-100-144.net) |
| 21:38.47 | *** mode/#bzflag [+v spldart] by ChanServ |
| 21:41.24 | spldart | ok narrowed the problem to a software update on my pc. I have a backup install from a week ago that I hope to use to find what changed in the OS that caused the monitor spanning issue. |
| 21:42.01 | spldart | Thanks for the idea to grab old cold and build to test. |
| 21:42.18 | spldart | I'm thinking they may have changed my video driver at this time. |
| 21:49.43 | *** join/#bzflag galileo_ (~QUJAAAAAA@d216-108-171-73.nt.northwestel.net) |
| 22:54.05 | blast007 | are you running Debian? |
| 22:55.26 | blast007 | if so, check in /var/log/apt for history.log or the various gzipped ones that logrotate rotated out |
| 23:03.43 | spldart | deb 9.4 yeah |
| 23:03.48 | spldart | I'll take a look |
| 23:09.46 | spldart | a bunch of library files for nouveau stand out. I really need to compare loaded modules now to a backup from a week ago. But that hdd is temp disconnected for another project. |
| 23:12.54 | spldart | In fact. I'm now thinking it may be my attempt to get steam running on this rig a second time that fouled bzflag. |
| 23:14.10 | spldart | Worst case scenario I can shutdown, unplug monitor 2, reboot and play all I want. |
| 23:39.17 | macsforme | tupone: yeah, we do some pretty weird overrides... I ran into them too when I did the OpenGL ES port |
| 23:42.56 | blast007 | macsforme: that in reference to the mtune thing or to the #ifndef thing? |
| 23:43.38 | macsforme | the latter |