In fact, that would make me very happy! You can create issues on github for errata in the manual btw. Please create one for this, too. 

How was the documentation originally written? I'm guessing it wasn't just written in HTML. 

With pandoc enhancements. If you wish to edit the docs and submit pull requests, we should chat so that we can set up the toolchain. 

Alright, shoot me an email or hit me up on IRC. I've been meaning to learn how to get around Github better so it'd be nice to get the chance to educate myself. 

Thanks SleepwalkR! 

i'm having a huge problem with Trenchbroom (2.0.0 RC1)
my compilating and launching profiling aren't being saved, i can set them, and use them, but if i close the program, and open it again, they are gone.

also, i'm having one more related issue, there is this old compiling profile that i wan't to delete, but i can't, it crashes trenchbroom instantly. 

sadly its a known issue: https://github.com/kduske/TrenchBroom/issues/1640

I THIIIIINK you could get them to save by opening a previous version of Trenchbroom, creating them in there and then they SHOULD transfer to the new version as well.

same for deleting the unneeded one. 

okay thanks 

also, i'm having one more related issue, there is this old compiling profile that i wan't to delete, but i can't, it crashes trenchbroom instantly.

This is not a known issue. Can you please submit a crash report on github that includes the file which contain your compilation profiles for Quake? The file is named "CompilationProfiles.cfg" and where exactly you can find it depends on the platform. 

I figured the two issues to be related to one another? Settings not saving or deleting? 

Download here: TrenchBroom 2.0.0 Release Candidate 2 is out: https://github.com/kduske/TrenchBroom/releases/tag/v2.0.0-RC2

Changes
- #1655: Ensure that worldspawn colors are treated correctly in smart entity color editor.
- #1655: Show color editor for any entity property matching `*_color`, `*_colour`, or `*_color2`.
- #1655: Properly set selected colors in smart color editor. Switch smart editors in idle event as opposed to in reaction to row selections.
- #1659: Ensure that points on the boundary are not added to a polygon. (#1662)
- #1661: Make sure to reset fly keys when 3D view loses focus. (#1663)
- #1653: Create a log file and add it to crash report. (#1657)
- #1656: Don't start a face drag in brush tool if there is no face under the mouse. (#1658)
- #1649: Fix bounding boxes of item_artifact_* in Quake.fgd
- #1646: Set selected texture when the user clicks on a texture in the texture browser. (#1647)
- #1648: Remove unused image from Linux build.
- #1640: Fix a bug that prevented game engine profiles from being persisted properly. (#1643)
- #1641: Print an error message when an error occurs while interpolating EL expression in compilation window. (#1644)
- #1638: Show message dialog when an exception occurs while launching a game engine (#1642)
- #1624: Change website to redirect to github for downloading releases. 

 

nice

i will continue to report new crashes

RC1 is crashing a lot less than the previous builds 

It's fantastic to see how much progress has been made, thanks SleepwalkR and everyone else involved.

Could you also provide SHA256's alongside the releases? pretty please 

 

https://github.com/kduske/TrenchBroom/releases/tag/v2.0.0-RC3

Getting fewer bug reports lately... either it's getting stable, or fewer people use TB. 

its defintely getting more stable and i cant wait for you to start hammering out those 2.1 features ;) 

 

Glad to hear it. 

I dipped into tb2 a bit more recently. Will probably consider changing to it full time on my main machine. The ui stuff is a bit cramped on my surface though 

 

Thanks, unfortunately MD5 has been unsafe for quite a long time now.

I apologize for not contributing but I'm away from my desktop and there's no release for my current os. (I've never had much luck compiling) 

So that's all I can do. Anyway, I think these checksums can only ever be used to verify the integrity of the downloaded file. They cannot be used to check whether the file was tampered with on the server. If someone was able to do that, they would also be able to change the checksum files. 

Still a bit of a Github Noob, even after all this time spent submitting TB issues (over 30 now I think!), so I'm not sure if contributing a comment to a closed issue will be seen...

https://github.com/kduske/TrenchBroom/issues/1560#issuecomment-277413575 

Yep, I get notifications on Github and emails for comments on closed issues, should be the same for SleepwalkR