search

thenayr / Half-Life-Alyx-SDK

Automates the creation of a Half Life Alyx standalone SDK
54 stars 6 forks source link

Hammer Editor crashes every time I open the model browser #5

Open Nintynuts opened 4 years ago

Nintynuts commented 4 years ago

I tried running as administrator, but it makes no difference. I also get this error at startup: image All I'm trying to do is export some models, which I can't do by File > Export As.. in the model viewer because of this: image (Both Half-Life: Alyx and SteamVR verified fine) and: image (which I believe is a general issue with source 2 models) then the SDK crashes.

So, I was trying this technique of adding it to a map, which causes the editor to crash when I click on the models tab: image

Any suggestions to get around this?

Thanks

Nintynuts commented 4 years ago

I figured out that it's possible to decompile textures using VRF and import models by dragging them into the editor from windows, but it could still be better!

TrainDoctor commented 4 years ago

Have you tried extracting the models and assets from pak01_dir.vpk using GCFScape? I've found that when I extracted stuff using VRF it tended to be a bit iffy. Wish I could help more.

Nintynuts commented 4 years ago

@TrainDoctor I think that neither GCFScape nor VRF is capabable of decompiling vmdl_c model files from HL: Alyx. When decompiling with VRF the file size is tiny and it won't open, viewing it crashes VRF. As I said, I managed to export the meshes with that trick from hammer. I am missing things like animations and attachment points, but I can live without those for my purposes.

KayvK commented 4 years ago

The same happens to me, but instead of the models tab crashing, the material tab crashes.

TrainDoctor commented 4 years ago

To return to this issue

Copy all the non-asset folders and files (hammer config stuff etc) from your bootleg tools and delete all the assets you downloaded. This is the first and only real way of solving an issue like this with such little actual context provided.

Then, using GCFScape, extract all relevant assets from pak01_dir.vpk into a folder near the bootleg tools after having done the setup. Next, take the files (put in a folder called root) into: ~/BootlegToolsFolder/game/hlvr

Although I'm sure you already know how to do the above, I'm covering my bases just in case.

  1. First error will always be encountered with bootleg tools. Ignore it.
  2. These are bootleg tools. Some things aren't going to function. 🤷 (especially when trying to do a "technique" developed on a different branch of the engine).

This is not a problem for @thenayr to resolve nor could he address it. Suggest this issue be closed.

Nintynuts commented 4 years ago

@TrainDoctor The context is that I used the tool in this repository as the instructions suggested.

Will extracting them with GCFScape instead of VRF really make any difference? Why? Isn't GCFScape an old Source 1 tool, whereas VRF is made for Source 2 games, which HL:A uses? If GCFScape is genuinely a more reliable tool, shouldn't this tool recommend using it?

~If the first dialog is a known issue, it should be documented.~ Just noticed it is there, either I missed it before or it's been added since I last looked. If there is no way to select models from the model browser or materials from the material browser (I think actually any asset browser), is there any point to these tools at all?

These seem like issues that need solving or at the very least documenting. And the 'technique' I'm trying to use isn't some obscure hack, it's dragging assets from the browser, surely that should work? And I can add assets by adding them via dragging in the desired model from windows, so the 'technique' in principle does work.

TrainDoctor commented 4 years ago

VRF is still heavily in development and GCFScape continues to be the best tool for the job in my experience.

In regards to the model and material editors, those are broken due to lack of missing assets/data due to the bootleg tools.

We are quite literally "stitching" one version of S2 into another, newer and different version. Don't expect anything to work regardless of how easy or simple it should seem.

KayvK commented 4 years ago

Restarting my computer seemed to fix the issue. Not sure what caused it.