Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2d model wireframe/model picker not working with standalone setup #4

Open
squeek502 opened this issue Mar 31, 2015 · 4 comments
Open

Comments

@squeek502
Copy link
Member

Fortress Forever redistributes Source SDK Base 2006, but there are issues when the gameinfo.txt loaded by Hammer does not set SteamAppId to 215 (Source SDK Base 2006's appid).

From #3:

certain things appear not to get loaded properly when Hammer is configured using the instructions in the readme (a bunch of editor-specific things like 2d-view displacements, player spawns, info_overlays, etc get drawn as ERROR).

Need to figure out what those assets are and make sure they're included with our redistributed SDK files.

EDIT: These files are found in common/SourceSDK/vpks/depot_211_dir.vpk

@squeek502
Copy link
Member Author

So, some of this can be fixed by copying the assets from the SourceSDK vpk (materials/models) in a path specified in our gameinfo.txt, but there are two lingering problems:

  • Models in the 2d view show the missing texture instead of the proper wireframe texture
  • The model picker scheme is totally broken

So, we need to figure out a few things, and I'm not sure how to go about doing that:

  • Find what material is used for model wireframes in 2d views and where it's trying to be loaded from
  • Find what scheme the model picker usually uses and where it's trying to be loaded from

If we get this figured out, we can keep the Hammer setup self-contained. Until then, I guess I'll switch things back to requiring a separate installation of Source SDK Base.

@squeek502 squeek502 changed the title Certain editor assets not loading with the new setup 2d model wireframe/model picker not working with standalone setup Mar 31, 2015
squeek502 added a commit that referenced this issue Mar 31, 2015
 * See #4
 * Needs a common/Fortress Forever/sdk/gameinfo.txt in the FF install
@ddm999
Copy link

ddm999 commented May 18, 2015

Using the Source SDK 2013 Multiplayer version of the editor models copied to FF's HL2 directory works fine for me in both 3D and 2D viewports.

working hammer

May be an issue with the older SourceSDK models being bugged out or something, really have no idea.

As for the model picker not working, I have no idea, but you can use the settings to enable the non-VGUI model selector (basically a file browser, but it shows all model files across the game's folders).

(Tools > Options > General > Untick "Use VGUI model browser")

EDIT: This doesn't fix the info_overlay texture, but does every other model, from what I can tell.

@mvoolt
Copy link

mvoolt commented Aug 17, 2023

So, some of this can be fixed by copying the assets from the SourceSDK vpk (materials/models) in a path specified in our gameinfo.txt, but there are two lingering problems:

  • Models in the 2d view show the missing texture instead of the proper wireframe texture
  • The model picker scheme is totally broken

So, we need to figure out a few things, and I'm not sure how to go about doing that:

  • Find what material is used for model wireframes in 2d views and where it's trying to be loaded from
  • Find what scheme the model picker usually uses and where it's trying to be loaded from

If we get this figured out, we can keep the Hammer setup self-contained. Until then, I guess I'll switch things back to requiring a separate installation of Source SDK Base.

The model picker accesses resource\mdl*.res located at depot_212_dir.vpk\platform

12:49:28.1286472	hammer.exe	1188	CreateFile	C:\program files (x86)\steam\steamapps\common\fortress forever\sdk\resource\mdlpickerrender.res	PATH NOT FOUND	Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a
12:49:28.1296065	hammer.exe	1188	CreateFile	C:\program files (x86)\steam\steamapps\common\fortress forever\sdk\resource\mdlpickerinfo.res	PATH NOT FOUND	Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a
12:49:28.1302518	hammer.exe	1188	CreateFile	C:\program files (x86)\steam\steamapps\common\fortress forever\sdk\resource\mdlpicker.res	PATH NOT FOUND	Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a

As for the wireframe model material, I've no idea. I used Process Monitor from SysInternals to figure what the model picker uses

@YoYo178
Copy link

YoYo178 commented Sep 16, 2023

The model browser's main culprit seems to be the SourceScheme.res that's bundled with the Source SDK 2006's hammer editor, which only seems to be of 3 bytes (it has nothing inside it except a few newlines), and as the file exists, it appears as a "SUCCESS" in Process Monitor (thanks to @mvoolt) but as the file is literally empty, it eventually leads to stuff being missing

To fix this, I copied 2 files from the Source SDK 2013 Multiplayer's resource folder to Source SDK's (2006) resource folder

SourceScheme.res
sourceschemebase.res

FROM <STEAM_DIR>\steamapps\common\Source SDK Base 2013 Multiplayer\platform\resource
TO <STEAM_DIR>\steamapps\common\SourceSDK\bin\ep1\bin\resource

(Alternatively, the files can also be copied to <STEAM_DIR>\steamapps\common\Fortress Forever\sdk\resource but that would still require deleting the "null" SourceScheme.res file that's located in <STEAM_DIR>\steamapps\common\SourceSDK\bin\ep1\bin\resource, otherwise it simply loads the said "null" SourceScheme.res file over the actual file and the behavior stays as is)

And while it does seem to still complain about the resource\mdl*.res files as per Process monitor (as stated by @mvoolt in the above post), the model browser seems to work flawlessly, apart from a few lighting issues (though I suppose that's normal?).
It also seems to affect the 2d views to be like the modern hammer editors by adding measure values, entity names, entity types, etc

image
image
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants