Announcement

Collapse
No announcement yet.

Using mods (Killer Quake Patch) with EZQuake

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Using mods (Killer Quake Patch) with EZQuake

    We recently started playing killer patch quake after severel years away from it. Been running it with Nehahra quake but the networking is not that great and we have some ping issues.

    We recently downloaded EZQuake and I really like the new look and features of EZQuake. But I'm having trouble running my killer patch with it. I normally run -game killer in my command line but that doesn't work with EZQuake.

    CAn anyone give me instructions on how to run killer or any other mod with EZQuake. Thanks.

  • #2
    EZQuake is based mainly around QuakeWorld if im not mistaken.. If I were to suggest a server exe, it would be proquake.
    Want to get into playing Quake again? Click here for the Multiplayer-Startup kit! laissez bon temps rouler!

    Comment


    • #3
      I tried running killer patch with proquake and it doesn't quite work. Even though Proquake says it's 100% compatible with other netquake clients.

      It loads the opening screen for killer but when I try to start or join a server I get "Host Error: Could not load Progs\shelcase.mdl"

      Not sure what the hell that means. I can run winquake, glquake, and neharha all with the -game killer command. But when I run glpro -game killer I get that message.

      As for the EZquake, even though it's based on quakeworld shouldn't I still be able to run killer? You can run TF and other mods with quakeworld can't you?

      Comment


      • #4
        same issue

        Originally posted by scaramanga View Post
        I tried running killer patch with proquake and it doesn't quite work. Even though Proquake says it's 100% compatible with other netquake clients.

        It loads the opening screen for killer but when I try to start or join a server I get "Host Error: Could not load Progs\shelcase.mdl"

        Not sure what the hell that means. I can run winquake, glquake, and neharha all with the -game killer command. But when I run glpro -game killer I get that message.

        As for the EZquake, even though it's based on quakeworld shouldn't I still be able to run killer? You can run TF and other mods with quakeworld can't you?
        I have the same issue with the killer quake pack 2.2z and glpro380.exe
        Have you a new solution ?
        Thanks

        Comment


        • #5
          The shellcase might be an MD3. I'll check this out here in a min.
          Quakeone.com - Being exactly one-half good and one-half evil has advantages. When a portal opens to the antimatter universe, my opposite is just me with a goatee.

          So while you guys all have to fight your anti-matter counterparts, me and my evil twin will be drinking a beer laughing at you guys ...

          Comment


          • #6
            That's very strange. ProQuake seems to hate that shelcase.mdl for reasons unknown. Even stranger since GLQuake 0.98 loads it fine.

            My guess would be that there is a discrepancy between the id source release and the code in GLQuake 0.98 (if so, not first I've seen ... chase cam bug, r_mirroralpha missing, etc.)

            Definitely something interesting to look into.

            In either case, Enhanced GLQuake runs it just fine and I'd definitely recommend that engine for playing mods.

            Enhanced GLQuake: http://user.tninet.se/~xir870k/glquakebjp.zip

            Enhanced GLQuake's highest concern is compatibility and it does a very good job with that. The author has even implemented obscure bug-fixes to solve small issues for individual mods. Quite an engine, really.
            Quakeone.com - Being exactly one-half good and one-half evil has advantages. When a portal opens to the antimatter universe, my opposite is just me with a goatee.

            So while you guys all have to fight your anti-matter counterparts, me and my evil twin will be drinking a beer laughing at you guys ...

            Comment


            • #7
              That error message comes from the ProQ cheatfree protection code, maybe disabling that will help?

              Otherwise the error message indicates a case error; "Progs" should be "progs" if the file is inside a pak. Although this error should then show up in most engines.

              Comment

              Working...
              X