ZDoom

I guess you owe me an apology Nah, just kidding.

Probalby because that build was broken beyond repair. I guess the Fluidsynth issue was just one of many. With my privately built version all works as it should.

Alot of svn was taken down. Why?

Fluidsynth worked perfectly with 252, with 288 it isn't even detected.

However, the point is rather moot since 288 was taken down from the download site.

Graf Zahl wrote:The person doing the builds must have forgotten to update the tags when pulling from the repo. It should read g1.9pre-xxxxxx, but unfortunately pulling tags is not automatic when using TortoiseGit.

Well, it reassures me to know it wasn't entirely my fault.
Still, from now on I know not to try to correct people on builds.

As for this bug, I just tested it with a 4 day old build and Fluidsynth just works at it always had. The problem must be on your end.

The person doing the builds must have forgotten to update the tags when pulling from the repo. It should read g1.9pre-xxxxxx, but unfortunately pulling tags is not automatic when using TortoiseGit.

The numbers of a development build are largely useless to the average user. The date/time stamp is easily the better indicator, along with the fact that any development build that is outdated by an official release will have no reason to be hosted anywhere any longer, thus largely unobtainable. So if a dev build is up and available, the bet is pretty safe that it's newer than official.

Like I said, I'm totally confused with these numbers, it seemed to me like 1.8.2 would be more recent.

TheMightyHeracross wrote:You're outdated.
1.8.2 is out.

gzdoom-g1.8.1-288-g759139e is from October 5th. GZDoom 1.8.2 is from June 23rd.

Hmm... wait a second.
The download (from the official GZDoom website) says 1.8.02, while the .exe says 1.8.2.
I'm confused.

-

As of g1.8.1-288-g759139e, the fluidsynth doesn't work. Is there a new command for it or something?