TrenchBroom 2019.5 RC 3
Textures Not Shown In Browser
Hi. just installed a fresh version on win10 and created a new q2 map, but textures are not shown in texture browser, only black squares with names. any suggestions on that?
looks like this bug is only in 2019.5 RCs, 2019.4 works fine
TrenchBroom 2019.5 RC5
TrenchBroom 2019.5 RC6
There was a bug that would result in TB not reading its preferences. RC6 fixes it: https://github.com/kduske/TrenchBroom/releases/tag/v2019.5-RC6
Adds ASE support, better rotate handle and visual improvements.
Get it here: https://github.com/kduske/TrenchBroom/releases/tag/v2019.5
Hello, I am working on one map in q3 format. I updated TB (sorry, I do not remember which version I had before). Now when I open the map it just crashes. And here is the crash file:
OS: Windows 7 (build 7601, Service Pack 1), 64-bit edition
wxWidgets Library (wxMSW port)
Version 3.1.1 (Unicode: wchar_t, debug level: 1),
compiled at Feb 18 2018 18:36:35
Runtime version of toolkit used is 6.1.
GL_RENDERER: Intel(R) HD Graphics 4000
GL_VERSION: 3.3.0 - Build 220.127.116.1112
TrenchBroom Version: 2019.6
TrenchBroom Build: v2019.6 Release
Reason: std::exception: bad allocation
I renamed the textures folder so the editor could not find it and now the map can be opened! After that I disabled all texture collections on the map and I gave the correct name for textures folder so editor could find it. After I add one texture collection by one and in one moment the map crashes again. I dont know how it works. May be the editor has some limitations for allocated memory. How can I fix that?
Can you post the map that crashes at http://github.com/kduske/TrenchBroom/issues
please? Using any .pk3's with third party textures or all stock q3 textures?
Yes Post An Issue Please
I suspect you are loading too many texture collections and run out of memory. Please also post your machine specs such as how much memory it has.
Reply To Ericw And SleepwalkR
Hi! Thanks for reply!
In editor I am using textures, which are located in folders, and I dont use any archives for editing maps. I am using my own textures. I thought that the problem can be in one of the textures (may be format is incorrect or some texture crashes the editor by some other reason). So that would mean that some of my texture catalogues contain the "problem" texture and I tried to find it. But each catalogue (folder with textures) can be opened freely without any crashes. But if I try to open more than 3 texture collections the editor crashes. Seems like the problem is in allocated memory
My laptop is 7 or 8 years old but I dont think that it has not enough memory to open the map. I have 8 gb of RAM, intel core i-7-3600 processor and Geforce 650m (idk if this information is needed).
I wonder if there are some limitations for the RAM that can be used in editor? If yes, how can I change it?
How Many Textures Are You Trying To Load In Total?
Also Can You Give A Total Of The Disk Space That These Textures Occupy
Textures occupy 465 mb of disk space. There are 1034 textures in total
DUSK SDK WILL HAVE TRENCH BROOM !
TrenchBroom 2020 Release Candidate 1
It's been a long time since the last release. This one is coming with a lot of changes and bug fixes:
TrenchBroom 2020 Release Candidate 2
This release candidate contains a lot of bug fixes and a new builtin dark theme, together with new icons that work better for both light and dark environments.
Nice Guide For The Compile Menu
Is it safe to overwrite v.2020.2 or should I delete it first? And if later, where does TB store building tasks config?
Any preferences or configurations you've done are stored in a place that depends on your OS.
macOS ~/Library/Application Support/TrenchBroom