Author Topic: Nightly (Windows): 31 Dec 2015 - Revision a236303  (Read 1123 times)

0 Members and 1 Guest are viewing this topic.

Offline SirKnightly

  • George or Keira?
  • 212
Nightly (Windows): 31 Dec 2015 - Revision a236303
Here is the nightly for Windows on 31 Dec 2015 - Revision a236303

Open non-feature issues in Mantis: 124

Group: Standard
fso_Standard_20151231_a236303.7z
MD5Sum

Group: SSE
fso_SSE_20151231_a236303.7z
MD5Sum

Group: AVX
fso_AVX_20151231_a236303.7z
MD5Sum

Group: NO-SSE
fso_NO-SSE_20151231_a236303.7z
MD5Sum

Code: [Select]
------------------------------------------------------------------------
commit d4d805d
Author: DahBlount <Sun Dec 27 22:07:31 2015 -0700>
Commit: DahBlount <Wed Dec 30 23:44:04 2015 -0700>

    Move turret_enemy_objnum check further up in block and change to Assertion
 code/ai/aiturret.cpp | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

------------------------------------------------------------------------
commit 8a2eec5
Author: Karajorma <Wed Dec 30 16:56:50 2015 +0800>
Commit: Karajorma <Wed Dec 30 16:56:50 2015 +0800>

    Fix the issue with repeat counts first discovered on this thread http://www.hard-light.net/forums/index.php?topic=90763.msg1801379#msg1801379
 code/fred2/eventeditor.cpp | 11 +++++++++++
 1 file changed, 11 insertions(+)



 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Nightly (Windows): 31 Dec 2015 - Revision a236303
Starting with this Nightly, debug symbols should show up in error messages without needing to rename the symbol file.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline niffiwan

  • 211
  • Eluder Class
Re: Nightly (Windows): 31 Dec 2015 - Revision a236303
Eeeeeeexcellent
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...