OpenXcom Forum
OpenXcom => Open Feedback => Topic started by: BlackLibrary on April 13, 2014, 03:07:26 am
-
<vent>What the heck is going on? You folks are going berserk on the builds and its scary. I want to test, but its a waste to test midstream of 4+ builds done in one day. Especially with the vague and or, dare I say it, painful, comments you leave for the rest of us to consume. Do what you do, but you can at least put 10 cents worth of comments up for folks to know whats changed.
Its not a latest nightly. Its a bug fest.</vent>
openxcom_git_master_2014_04_12_2313.zip - built 2014-04-12 21:16
Warboy, Sat Apr 12 23:13:11 2014
hahahahahha enjoy the difference this makes.
openxcom_git_master_2014_04_12_2221.zip - built 2014-04-12 20:24
SupSuper, Sat Apr 12 22:21:07 2014
Please don't crash please don't crash please don't crash
openxcom_git_master_2014_04_12_2207.zip - built 2014-04-12 20:10
Warboy, Sat Apr 12 22:07:31 2014
fix kneel button.
openxcom_git_master_2014_04_12_2132.zip - built 2014-04-12 19:35
Warboy, Sat Apr 12 21:32:10 2014
hail C++ser
openxcom_git_master_2014_04_12_2106.zip - built 2014-04-12 19:09
SupSuper, Sat Apr 12 21:04:55 2014
Fixed serious textlist crash (thanks to LouisdeFuines for testing)
SupSuper, Sat Apr 12 20:26:24 2014
Linux users don't like spaces. :P
openxcom_git_master_2014_04_12_1956.zip - built 2014-04-12 17:59
Daniel, Sat Apr 12 19:56:37 2014
Merge pull request #810 from cfailde/undefined_reference
Fix compilation on linux
Carlos Failde, Sat Apr 12 19:41:29 2014
Fix compilation on linux
openxcom_git_master_2014_04_12_1813.zip - built 2014-04-12 16:17
Warboy, Sat Apr 12 18:13:59 2014
fix a few textlist issues
openxcom_git_master_2014_04_12_1614.zip - built 2014-04-12 14:17
Warboy, Sat Apr 12 16:14:57 2014
cap encumberance
openxcom_git_master_2014_04_12_1513.zip - built 2014-04-12 13:16
Warboy, Sat Apr 12 15:13:12 2014
fix English
openxcom_git_master_2014_04_12_1436.zip - built 2014-04-12 12:39
Warboy, Sat Apr 12 14:36:25 2014
add missing energy recovery values
openxcom_git_master_2014_04_12_1404.zip - built 2014-04-12 12:08
Warboy, Sat Apr 12 14:04:05 2014
may as well keep that consistent
openxcom_git_master_2014_04_12_1401.zip - built 2014-04-12 12:04
Warboy, Sat Apr 12 14:01:37 2014
further fix for base res
don't allow it to go below the minimum.
openxcom_git_master_2014_04_12_1346.zip - built 2014-04-12 11:50
Warboy, Sat Apr 12 13:46:58 2014
fix for screen res issue
openxcom_git_master_2014_04_12_1343.zip - built 2014-04-12 11:46
Warboy, Sat Apr 12 13:43:17 2014
get the AI to store a vector of reachable tiles
and use that to skip pathfinding where applicable:
decreases AI think time expontentially, also avoids the AI hang
when they run out of energy because now Dijkstra is aware of it
Warboy, Sat Apr 12 13:23:32 2014
make Dijkstra method account for energy
openxcom_git_master_2014_04_12_1112.zip - built 2014-04-12 09:14
Warboy, Sat Apr 12 11:12:23 2014
my bad, soldiers don't have unitRules
openxcom_git_master_2014_04_12_1047.zip - built 2014-04-12 08:50
Warboy, Sat Apr 12 10:47:18 2014
add energy recovery stat to units
Warboy, Sat Apr 12 10:46:35 2014
reorder some things in the ruleset
openxcom_git_master_2014_04_12_0829.zip - built 2014-04-12 06:32
SupSuper, Sat Apr 12 08:29:06 2014
Ported popular XcomUtil/Extender mods (thanks MKSheppard), can serve as examples for the community.
SupSuper, Sat Apr 12 08:22:55 2014
Fixed TextList and ruleset loading bugs.
openxcom_git_master_2014_04_12_0406.zip - built 2014-04-12 02:11
SupSuper, Sat Apr 12 04:06:21 2014
- Fixed edge scroll / drag scroll conflict.
- Organized Advanced Options screen.
- Code cleanup.
-
At least they have a funny sense of humor. It's the only reason I scroll through the nightly build page.
-
We gotta crack down on those bugs if we're gonna get 1.0 out. :P (thanks for all the reports lately btw)
Really though, you read the disclaimer. The nightly builds tap directly into the developer codebase. They are automatically produced out of every single code change we make, no matter how insignificant. A lot of stuff probably won't even make sense to you, and it's not really supposed to. But you can trust every change is at least making the game slightly better in some way. :)
-
But you can trust every change is at least making the game slightly better in some way. :)
"Please don't crash please don't crash please don't crash" I would consider that making it better. :)
-
2 hardcore 4 you? :P
-
BlackLibrary is trying to test each build, so good work fellow :)
I only grab the latest to play, not test, but I'll barely report anything when the bug bothers me hehehehe.. Like that hightlighting issue in the Crew screen, thanks for fixing it quickly!!
-
Lol...stress from work. Wasn't trying to test the nightlies, but its painful when you have a fun campaign with mods, and -boom- there is an issue that you don't know why. In my case, it kept crashing on the start of my base getting assaulted (something I've been eagerly waiting for months to happen!)
So...I checked the nightlies and tried one. Still crashed. Walked away to handle the real world. Then I looked at the "nightlies" and boom...there are a bunch of new builds. Tried them again...and boom, base mission is still failing. Diagnosed it as best as I could and then checked the "nightlies" again and a bunch more. I just wanted to play...but can't...the bug is in the way. So, I just wanted to test and if there is a bug, post it. But instead I said -screw it- and deleted the whole campaign and started fresh. So I end up not reporting the game crash bug at all. Perhaps it will never see the light of day ever again. IDK.
Later, when I had a few minutes of free time, I went to check the "nightlies" for shits and giggles and, yep...more changes. "Which nightly should I use?" I thought to myself. I want to start a new game...but can't do it on a flawed build, or a build that says "please don't fail, please don't fail".
How do I report the bug when who knows what may have initiated it...or if its from testing different builds that may have had an inadvertent effect on each other. Whatever. Each build must have some value. Hell, I could pull the code down again and do a windiff or whatever, but it was just irksome.
Regardless, there is a concept of testing your own code build. You don't push code (that others -have- to merge!) that you even think might fail. A code of honor amongst us developers, or so I thought.
Don't get me wrong, I do appreciate the considerable effort and energy expended. But each build should do exactly what it says on the tin. LOL!
Thanks folks.
-
I'm not entitled to speak on devs' behalf, but what you described - the game crashing on X-Com base defence - if a pretty major bug. I had a base assault recently and it went fine; plus, I'm sure someone would start to lose their shit over something that major. So perhaps this is an issue unrelated to the nightly builds?
There was one recent case of a nightly build actually screwing something up, which was a saving problem; it was dealt with very quickly. Other than that, there was nothing to affect gameplay. Many players download daily (or even more often, like you and me), so I think such a bug would be caught...