EDIT: Oh my GOD GitHub's UI is garbage. Doesn't even stop me from hitting enter accidentally before I've entered a description. And no way to delete the issue once it's been posted. Well anyway...
In vanilla Hammer, the Configurations dropdown in the Expert compile window is prepopulated with a few stock configs. The default one (that runs when you use Normal mode), Full Compile (which is actually missing things like -staticproplighting), etc. In Hammer++, freshly installed, there's nothing. Default is there but it's empty. There doesn't even seem to be any documentation on the Valve Dev Wiki as to what the stock configs even are, so I have to quit out, open regular Hammer, write it all down, and then come back into Hammer++ and copy them over. I feel like this wasn't the intended behavior? Maybe it's meant to load the configs from Hammer's own data files but it's looking in the wrong place?
EDIT: Oh my GOD GitHub's UI is garbage. Doesn't even stop me from hitting enter accidentally before I've entered a description. And no way to delete the issue once it's been posted. Well anyway...
In vanilla Hammer, the Configurations dropdown in the Expert compile window is prepopulated with a few stock configs. The default one (that runs when you use Normal mode), Full Compile (which is actually missing things like -staticproplighting), etc. In Hammer++, freshly installed, there's nothing. Default is there but it's empty. There doesn't even seem to be any documentation on the Valve Dev Wiki as to what the stock configs even are, so I have to quit out, open regular Hammer, write it all down, and then come back into Hammer++ and copy them over. I feel like this wasn't the intended behavior? Maybe it's meant to load the configs from Hammer's own data files but it's looking in the wrong place?