Author Topic: NEW RELEASE IMMINENT - PLEASE REPORT BUGS  (Read 2518 times)

0 Members and 1 Guest are viewing this topic.

Offline The E

  • He's Ebeneezer Goode
  • Moderator
  • 213
  • Nothing personal, just tech support.
    • Steam
    • Twitter
NEW RELEASE IMMINENT - PLEASE REPORT BUGS
Hi folks! It's been a while since our last release, and so it's time to once again start the release cycle. As such, we need you (yes, you!) to bring bugs to our attention.

This will be the actual real final release to use DirectInput; After this is done, the much talked about merge of the SDL Everywhere featureset will finally happen.
If I'm just aching this can't go on
I came from chasing dreams to feel alone
There must be changes, miss to feel strong
I really need lifе to touch me
--Evergrey, Where August Mourns

 

Offline Talon 1024

  • 29
  • How do you turn this on?
    • Mods, Games, and Stuff
Re: NEW RELEASE IMMINENT - PLEASE REPORT BUGS
Now that the FS2 SCP repo on GitHub has an issue tracker of its own, what is the preferred issue tracker for FS2_Open?

On the other hand, I've reported an issue on Mantis here.
To understand religion, you need to understand morality first. | WCSaga website | WCSaga Forum | 158th website | 158th forum | Project Leader: WC: Hostile Frontier | WCHF Thread at CIC | Wing Blender | Twist of Fate | Multipart turrets on angled surfaces, tutorial included. | My Google Drive stuff | To convert speeds from WC to WCS, multiply both the cruise speed and the Afterburner speed by 0.15625 (5/32)

FS2 Mods I'm waiting on: Inferno 10th Anniversary
Current Project: Contestant Android app, Learn4Life iOS app, Blender Commander (importer).
The FreeSpace Font Foundry is back in action!

 

Offline m!m

  • 211
Re: NEW RELEASE IMMINENT - PLEASE REPORT BUGS
I did some more testing and the issue Talon 1024 mentioned doesn't happen in 3.7.2 on any platform I can test so it looks like a regression since then. That bug is a definite release blocker but hopefully should be easy to fix with git bisect :p

EDIT: The bug was introduced in 27d85189eafb612e979649355d5ddf3000ea0bcd, a fix for this is being worked on.
EDIT2: Bug is fixed in master.
« Last Edit: September 06, 2015, 07:47:12 am by m!m »

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: NEW RELEASE IMMINENT - PLEASE REPORT BUGS
Now that the FS2 SCP repo on GitHub has an issue tracker of its own, what is the preferred issue tracker for FS2_Open?
I don't think there's been any kind of official decision on when it is or is not preferable to use GitHub's issue tracker, but there's been something of a de facto division of "if somebody sees a problem in the code (and doesn't want/know how/have time to make a PR for it), make a GitHub issue; otherwise, make a Mantis issue", which seems sensible enough. In purely practical terms, we have too many issues in Mantis to make switching to a new issue tracker for everything anywhere close to "smooth".

There are pros and cons to making an issue on either system. On the one hand, GitHub issues get automatic integration in GitHub discussions (mentioning the number autocreates a link, and makes a note that a reference to that issue has been made along with a backlink on the issue itself). On the other hand, Mantis has features like the Roadmap, which let us see issues targeted for a specific release and what their status is. While there's no automatic resolving of issues like there was with SVN, it's probably possible to find a way to set one up for Git.

Given that, I'd personally recommend still using Mantis for the typical end-user.
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 jr2

  • The Mail Man
  • 212
  • It's prounounced jayartoo 0x6A7232
    • Steam
Re: NEW RELEASE IMMINENT - PLEASE REPORT BUGS
Any way to easily make GitHub issue tracker sync with Mantis?

 

Offline Yarn

  • 210
Re: NEW RELEASE IMMINENT - PLEASE REPORT BUGS
I noticed just now that the grid effect used in the ship and weapon selection screens isn't working properly. When the line starts to draw the grid, instead of the grid being revealed gradually, the whole thing appears immediately. The ship and weapon models seem to be OK, though.

Once I find the change that introduced this bug, I will post either a GitHub issue or a pull request.

EDIT: Here's the GitHub issue: https://github.com/scp-fs2open/fs2open.github.com/issues/347
« Last Edit: September 15, 2015, 07:42:49 pm by Yarn »
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178