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

FGDs and dxsupport.cfg missing from SDK Base Multiplayer #9

Closed
Artfunkel opened this issue Jun 27, 2013 · 17 comments
Closed

FGDs and dxsupport.cfg missing from SDK Base Multiplayer #9

Artfunkel opened this issue Jun 27, 2013 · 17 comments
Assignees

Comments

@Artfunkel
Copy link

@Artfunkel Artfunkel commented Jun 27, 2013

Mappers can't create entities in Hammer and the engine defaults to DX8 every time it loads.

@HenryDorsett

This comment has been minimized.

Copy link

@HenryDorsett HenryDorsett commented Jun 27, 2013

Just to make sure all the bases are covered, this problem also exists, as described, in SDK Base Singleplayer.

@JoeLudwig

This comment has been minimized.

Copy link
Contributor

@JoeLudwig JoeLudwig commented Jun 28, 2013

This should be fixed in the singleplayer SDK base. If it's working there we'll apply the same fix to the Multiplayer base.

@ghost ghost assigned JoeLudwig Jun 28, 2013
@Artfunkel

This comment has been minimized.

Copy link
Author

@Artfunkel Artfunkel commented Jun 28, 2013

Singleplayer now has base.fgd but not HL2. Multiplayer has HL2 but not HL2MP.

@Artfunkel

This comment has been minimized.

Copy link
Author

@Artfunkel Artfunkel commented Jun 28, 2013

I've loaded up Singleplayer but it still defaults to DX8 despite the presence of dxsupport.cfg. I've validated to no effect. Other source games don't have this issue.

My dxdiag: https://gist.github.com/Artfunkel/5883898

@alfred-valve

This comment has been minimized.

Copy link
Contributor

@alfred-valve alfred-valve commented Jun 28, 2013

Run the game with "-autoconfig" and see if that helps. How are you determining you are launching with dx8 support?

@alfred-valve

This comment has been minimized.

Copy link
Contributor

@alfred-valve alfred-valve commented Jun 28, 2013

@Artfunkel , the SP build includes halflife2.fgd, it sounds like your SP base install is bad given your other bug report. Try a validate of the install.

@HenryDorsett

This comment has been minimized.

Copy link

@HenryDorsett HenryDorsett commented Jun 28, 2013

In reply to determining that's it's launching in DX8 mode, calling mat_dxlevel gives an output of it being set to 80, and under advanced video options, it reports the hardware DX level as being 8.0. As I'm having an identical problem, I'm first validating SDK Base 2013 Singleplayer, and then, if that fails, running with -autoconfig. I'll report back with results.

@Artfunkel

This comment has been minimized.

Copy link
Author

@Artfunkel Artfunkel commented Jun 28, 2013

For a moment there autoconfig did the trick for SP, but it's now back to starting with DX8. No change for MP.

Like Henry I've been paying attention to mat_dxlevel. I change it to 95 or 98 and everything is fine, but it's always 80 when I next start the game.

(I validated before writing my second comment and I do now have halflife2.fgd for SP, so that seems to be fixed. MP is still lacking hl2mp.fgd.)

@HenryDorsett

This comment has been minimized.

Copy link

@HenryDorsett HenryDorsett commented Jun 28, 2013

Did the validation, and I was missing one file, so that seems to be fixed, but it didn't resolve the error. Running -autoconfig on the SDK Base followed by the mod does seem to have resolved the issue, though.

@alfred-valve

This comment has been minimized.

Copy link
Contributor

@alfred-valve alfred-valve commented Jul 2, 2013

MP Base was updated with these missing files.

@Artfunkel

This comment has been minimized.

Copy link
Author

@Artfunkel Artfunkel commented Jul 3, 2013

The FGDs are sorted but MP doesn't have dxsupport.cfg and is still defaulting to DX8.

I've discovered through registry editing that the engine will never, ever overwrite an existing value at <game>\Settings\DXLevel_V1, even if you do mat_dxlevel 95;mat_savechanges. That's why the addition of dxsupport.cfg to SP had no effect on my system. Now that I've deleted the reg key SP mods start with dxlevel 95 as intended.

@fletcherdvalve

This comment has been minimized.

Copy link

@fletcherdvalve fletcherdvalve commented Jul 3, 2013

Files have been added an update has been released.

@Artfunkel

This comment has been minimized.

Copy link
Author

@Artfunkel Artfunkel commented Jul 3, 2013

Everything is sorted!

@tealsuki

This comment has been minimized.

Copy link

@tealsuki tealsuki commented Jul 4, 2013

This isn't entirely related to the SDK, but when all of the Half-Lifes were moved over to Steampipe, the DirectX issue is happening with those too (Except Ep2). I deleted the registry keys, and used -autoconfig, but this caused it to revert to a state with DX8 I'd call worse than safe mode. In addition to this, trying to force mat_dxlevel to 95 will usually result in the screen-space filter textures to unload(?)

Anyways, I fixed it by copying all the dxsupport files from [SDK Base]\bin\ to Half Life 2\bin
Might want to check to make sure those haven't disappeared on y'all

@Artfunkel

This comment has been minimized.

Copy link
Author

@Artfunkel Artfunkel commented Jul 5, 2013

...and nobody else noticed because we already had pre-SteamPipe HL2 settings in our registry.

@alfred-valve

This comment has been minimized.

Copy link
Contributor

@alfred-valve alfred-valve commented Jul 8, 2013

The HL2 beta adds the dxconfig files back, you should opt into it to double check :)

@tealsuki

This comment has been minimized.

Copy link

@tealsuki tealsuki commented Jul 8, 2013

I revalidated my HL2 install and it downloaded the dxconfig files without a problem, thanks alfred-valve! I'm going to do a quick experiment, but I think everything should be all good now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.