tyr-quake.exe has stopped responding

[Mindf!3ldzX]

So I will go a step further than most, and actually install TyrQuake, and here are the observations !

~Tyr-GLQuake defaults to an attempted 320x200 (failsauce on a modern OS)
~Tyr-GLQuake spits out the error "No RGB fullscreen modes available" and crashes

So I command line up with tyr-glquake.exe -width 1440 -height 900 -bpp 32 -zone 1024

~Tyr-GLQuake fired up just fine

[Grim Warlock]

mindfield's suggestion is misleading, please do not install some random additional files.

W LoadWadFile : couldn't load gfx.wad - Quake Wiki

As Johnny said, make sure your OS is not interfering.

Sorry it appears I was formatting the command line incorrectly, but I've done it the correct way this time and it still simply stops responding when I attempt to load TYR-Quake.exe. It doesn't show any error in the prompt.

I'd certainly know if a file or folder was in the wrong location as well, I've checked that 3 times and have also done multiple re-installs.

So I will go a step further than most, and actually install TyrQuake, and here are the observations !

~Tyr-GLQuake defaults to an attempted 320x200 (failsauce on a modern OS)
~Tyr-GLQuake spits out the error "No RGB fullscreen modes available" and crashes

So I command line up with tyr-glquake.exe -width 1440 -height 900 -bpp 32 -zone 1024

~Tyr-GLQuake fired up just fine

Every GL-based engine works perfectly on here, it's just that every software-based engine doesn't. TYR-GLQuake.exe does load, but almost everything appears to be white. I wasn't trying to use the GL one anyway, I'm trying to get the one with software mode to load.

[Mindf!3ldzX]

Sorry it appears I was formatting the command line incorrectly, but I've done it the correct way this time and it still simply stops responding when I attempt to load TYR-Quake.exe. It doesn't show any error in the prompt.

I'd certainly know if a file or folder was in the wrong location as well, I've checked that 3 times and have also done multiple re-installs.



Every GL-based engine works perfectly on here, it's just that every software-based engine doesn't. TYR-GLQuake.exe does load, but almost everything appears to be white. I wasn't trying to use the GL one anyway, I'm trying to get the one with software mode to load.

Alas I did the same thing for the software engine and the results was the same, D:\Games\ProQuake\tyr-quake.exe -width 1440 -height 900 -bpp 32 -zone 1024 = fully functioning through and through.

Open your Catalyst Control Center () go to information tab ,look at the Software section.

Driver Packaging Version 14.10.1006-140417a-171099C
Catalyst Version 14.4
Provider Advanced Micro Devices, Inc.
2D Driver Version 8.01.01.1390
2D Driver File Path /REGISTRY/MACHINE/SYSTEM/ControlSet001/Control/CLASS/{4D36E968-E325-11CE-BFC1-08002BE10318}/0000
Direct3D Version 9.14.10.01029
OpenGL Version 6.14.10.12874
AMD Catalyst Control Center Version 2014.0417.2226.38446
AMD Audio Driver Version 7.12.0.7718

On top of that, make sure your DirectX is completely up to date (DX9 and DX11.1 BOTH)
http://www.microsoft.com/en-us/downl...s.aspx?id=8109 <- DX9
http://www.microsoft.com/en-us/downl....aspx?id=36805 <-DX11

There is no reason that I can fathom why a brand spanking new computer would't run the Tyr client/engine, short of not being updated.

Best of luck getting your specific Quake choice running! I've reached the end of my proverbial rope HEH.

[Grim Warlock]

When I attempted to install DirectX 11 it came up with this error:

"Installer encountered an error: 0x80070422

The service cannot be started, either it is disabled or because it has no enabled devices associated with it."

I went into Services, and Windows Installer was not disabled.

I'm not using ATI, using NVIDIA. Here is the system information:

[Display]
Operating System: Windows 7 Home Premium, 64-bit (Service Pack 1)
DirectX version: 11.0
GPU processor: GeForce GTX 660
Driver version: 337.88
Direct3D API version: 11
Direct3D feature level: 11_0
CUDA Cores: 960
Core clock: 980 MHz
Memory data rate: 6008 MHz
Memory interface: 192-bit
Memory bandwidth: 144.19 GB/s
Total available graphics memory: 4096 MB
Dedicated video memory: 2048 MB GDDR5
System video memory: 0 MB
Shared system memory: 2048 MB
Video BIOS version: 80.06.58.00.64
IRQ: 16
Bus: PCI Express x16 Gen2
Device Id: 10DE 11C0 36251458
Part Number: 2030 0000

[Mindf!3ldzX]

Woops, dyslexic much mindz? I misread the OP, I had it backwards, woops again! My bad! I dunno bro, I wave the white flag and surrender.


I can tell you this though, its only going to get tougher to run the software rendered engines , Microsoft confirms DirectX 11.2 is a Windows 8.1, Xbox One exclusive | bit-gamer.net

If there was ever a time to find the next best thing, it would be now. Sorry I failed ya broseph.

[Spike]

its not that much of an issue, if you want software engines to continue running in the coming years, you could always port them to opengl instead.
and by that, I mean generating a texture and blitting that, rather than bluring all the textures and stuff.

1: make sure you use -startwindowed or whatever the command was. this ensures that it doesn't try to go fullscreen and fail from being unable to use 320*200 which windows doesn't really support any more.
2: you may need to disable dep. even if you're using the same os+service pack, an upgraded cpu can mean it actually works now (and by works, I means it crashes badly behaved programs, like winquake)
3: try -nosound, to rule out directsound-related issues (I think there's a -safe argument or something that disables a whole load of stuff.
other than that, no idea.

[Johnny Law]

Also just to be clear, while DirectDraw is deprecated it's not gone yet. There's obviously something odd going on here but it's not some universal Windows 7 hostility to Quake engines that use DirectDraw.

[Grim Warlock]

2: you may need to disable dep. even if you're using the same os+service pack, an upgraded cpu can mean it actually works now (and by works, I means it crashes badly behaved programs, like winquake)

My God, I am so fucking stupid! This was what was causing it to not run! Thank you!

Thanks for the help everybody ^^!