Problem with a Quake HD pack

[Joã0_P3dr0]

Well I downloaded a Quake HD pack here: Quake HD Pack mod - Mod DB


I followed the all the installation steps and when I started the darkplaces.exe, I got this "little problem"



How can I fix it? My OS is a Windows 7 Home Premium 32-bits and the resolution is on 1600X900, the GPU is an AMD M880G with ATI Mobility Radeon HD 4250. And yes, I am using a laptop with a PC monitor, because my laptop's display is broken. So, can someone help me with it?

[Spike]

Basically, what's happening is that the engine normally uses the old 8bit content that would normally be in pak0.pak to determine the sizes that this stuff should appear as.
without that stuff, it just uses the size of the replacement content. which is muuuch bigger.

press shift+escape to get at the console and type path
this should show a few pak or pk3 files. you need an 'id1/pak0.pak', with 339 files in it. It'll probably be displayed at the bottom of the list (lowest priority).
this file is present in the demo or whatever

[Syluxguy28O3]

Actually, no I didn't deleted the pak0.pak and I just have the Quake's shareware demo. I didn't bought the game yet

i think that might be the prob, from the sound of things.

[Joã0_P3dr0]

Thanks Spike, missing PAK0.PAK do this for me too. Joã0_P3dr0 probably deleted it by accident somehow.

Edit: Or maybe have copied pak0.pak from one of the mission packs, into id1\ folder instead of rogue\, or hipnotic\ folders.

Edit2: If you get it working and performance will be terrible - type into console: r_glsl_offsetmapping 0 and follow other performance advises from the readme.

Actually, no I didn't deleted the pak0.pak and I just have the Quake's shareware demo. I didn't bought the game yet

[_Smith_]

Thanks Spike, missing PAK0.PAK do this for me too. Joã0_P3dr0 probably deleted it by accident somehow.

Edit: Or maybe have copied pak0.pak from one of the mission packs, into id1\ folder instead of rogue\, or hipnotic\ folders.

Edit2: If you get it working and performance will be terrible - type into console: r_glsl_offsetmapping 0 and follow other performance advises from the readme.

[Spike]

last time I saw an issue like that it was because pak0.pak was missing.

[Joã0_P3dr0]

Hello Joã0_P3dr0, (what a nice nickname)

Did you already tried to play vanilla Quake with only Darkplaces engine ?
That is what I would do, if I encounter issues.
Make a folder called Quake and in it make a folder called id1.
Put the original Quake .pak files into id1 and download a new Darkplaces build, which you extract into Quake folder.
No preconfigured configs or anything.
Then start darkplaces.exe.

I tried it with just the Darkplaces, and it is working now. I think my laptop just wasn't handling well with the other stuff(Why? I have no idea). Thanks for the help Seven, and you too _Smith_

[Seven]

Hello Joã0_P3dr0, (what a nice nickname)

Did you already tried to play vanilla Quake with only Darkplaces engine ?
That is what I would do, if I encounter issues.
Make a folder called Quake and in it make a folder called id1.
Put the original Quake .pak files into id1 and download a new Darkplaces build, which you extract into Quake folder.
No preconfigured configs or anything.
Then start darkplaces.exe.

If you encounter the same issues, then it is not related to the Quake compilation. Your computer hardware/driver is most probably causing this.
You could open the console in game and type: vid_desktopfullscreen 1
Then quit and restart darkplaces and see if it works.
Because I was wondering why the screenshot you were posting has a resolution of 640x480, while your desktop resolution has 1600x900. It looks like you can only see a small part of your Quake (a 640x480 window of your 1600x900 Quake). That would explain the huge characters.
The above mentioned cvar forces darkplaces to use your desktop resolution in fullscreen.

If it doesnt help, you could try to run Darkplaces in window mode (start with a smaller resolution than your desktop).



If vanilla + DP works without issues, you could do the following in your Quake compilation:
Delete all the config files (Darkplaces will create new config after 1st start)

If it doesnt help, you should copy the replacement files from the Quake compilation (incl. .pak´s and pk3´s) one after the other into your vanilla + DP Quake to see which one is causing the issue.

This way you will most probably find out what is causing it.

Best of luck.


PS: If vanilla + Darkplaces refuses to work at all, you could try other andvanced Quake engines like FTEQW or DirectQ (to also try a DirectX version, if this works better for your laptop hardware !)

[_Smith_]

Probably your mobile chipset and its drivers are at fault. Maybe there is someone here with similar hardware to share experience ?
I haven't seen similar issue yet, is your ingame HUD borked too ? Anyone, any ideas ?

Since we ruled out csqc hud mod in moddb comments already, I can't think of anything in the pack that could cause it.