A setting to retain the individual visgroup states (collapsed/expanded) in Options would be nice.
Every time you open a map all the visgroups are expanded.
Many times (not always!) when you open a crash file, and on rare occasions when opening a (not crashed) VMF, some visgroups are collapsed. So it is possible for the application to track the indivual state of the visgroup or set the state when opening the file. Somehow.
And no idea if this is possible but plz remove the 128 limit cap on visgroups.
When creating a visgroup close or over the 128 limit cap Hammer++ will crash.
The new visgroup is fine when reopening the file but the next created visgroup WILL crash Hammer++ again. Etc.
I know that the old Hammer did this as well. So maybe its hardcoded?
A setting to retain the individual visgroup states (collapsed/expanded) in Options would be nice.
Every time you open a map all the visgroups are expanded. Many times (not always!) when you open a crash file, and on rare occasions when opening a (not crashed) VMF, some visgroups are collapsed. So it is possible for the application to track the indivual state of the visgroup or set the state when opening the file. Somehow.
And no idea if this is possible but plz remove the 128 limit cap on visgroups. When creating a visgroup close or over the 128 limit cap Hammer++ will crash. The new visgroup is fine when reopening the file but the next created visgroup WILL crash Hammer++ again. Etc. I know that the old Hammer did this as well. So maybe its hardcoded?