Widescreen Gaming Forum

Hi,

First, thanks to everyone here at WSGF giving excellent information

Second, Super thanks for this fix.

One problem I had was that I could not see my own health

Solution to this was to edit xpos in CHudLocalPlayerDisplay to "xpos" "r1000"

Not perfect, but I can at least see it.

Running on 3x1680x1050 (5040*1050)

If you're willing to make one for 5760x1080, I would be very grateful. There's no rush, though.. as I am fine playing with the HUD on the side monitors.. it doesn't really bother me. However, I'm sure others will be looking for that resolution as well :)

Yeah I'm willing...just really short on time now that the holiday weekend is past and I have some contract work due next week.

When I started it defaulted back to 640x480 (or whatever) then would not let me select anything above 3840x1024 in the options.

That's odd. The game itself wouldn't let you select your resolution in the options menu? Have you tried launching with the -w -h switches?

@danielj

Happy to help. Care to post an in-game screenshot when you can? Would help as reference data.

_________________
VirtualDub Game Recording Guide | BFME2 & RotWK Widescreen/Triplehead Mods

Hmm... guys and what about bun? Is there real risk of be buned using this? :cry:

Hmm... guys and what about bun? Is there real risk of be buned using this? :cry:

I will be submitting an inquiry to Valve concerning this mod/tweak. Hopefully it will get the all clear.

_________________
VirtualDub Game Recording Guide | BFME2 & RotWK Widescreen/Triplehead Mods

3) The game engine does not automatically see the extracted hudlayout.res file and use it instead of the one in the .vpk file. To correct this you need to HEX edit the .vpk:

Search for this text string:

Code:

scripts.hudlayout

and change something in hudlayout to rename the .res file within the .vpk, causing the engine to "not see" it. I did this:

Code:

scripts.mudlayout

This process might have to be repeated from scratch if a game update breaks the modded .res file. If this happens, the first thing to check is step 3--the pak01_dir.vpk file might have been updated. Try to hex-edit the filename again and see if the extracted hudlayout.res is recognized again. If not, start from scratch with Step 1.

I tried using two different hex editors and searching for the key, but they couldn't find it. I am wondering if you could detail a little more on how to accomplish this.

Here's what it looks like in HxD. Some editors display text with spaces so that could be the problem with a search.

_________________
VirtualDub Game Recording Guide | BFME2 & RotWK Widescreen/Triplehead Mods

Works now, good stuff.

Works now, good stuff.

Glad to hear it. Are you working on a particular res/AR?

General note: I've contacted Valve concerning VAC & this mod. Should hopefully have a response in a few days.

_________________
VirtualDub Game Recording Guide | BFME2 & RotWK Widescreen/Triplehead Mods

General note: I've contacted Valve concerning VAC & this mod. Should hopefully have a response in a few days.

Thank you! I really hope on positive answer! And waiting for it with pation :cheers

General note: I've contacted Valve concerning VAC & this mod. Should hopefully have a response in a few days.

I'm assuming that if you contacted support about it you will get a canned response that they cant tell you what VAC bans for. Skins require the same vpk edit that you are doing and they have never banned for skins.