HELLGATE IV - AW2 (by Freecrac)

[Wolfseye]

Map Name: HELLGATE 4 - AW2

Gametype: COOP

Map Creator: Freecrac

Map Description: On our way we can find some LFPs(no PSP used). To respawn we have to press the corresponding letter of the LFP. Order: Destroy all targets(red on radar).

PLEASE DONT FORGET TO RATE THE MAP BY CLICKING ON "RATE THREAD" RIGHT ABOVE THE POSTING !

[factoryfk]

For some reason my computer did not enjoy this game at all. When I got to the fire by the bunker it was all choppy (at the start) and went around the corner up the stairs I fell through and could see all the guys running around but coulnt shoot them. My vid card is up to date but who knows lol anyone else have this problem?

[freecrac]

Many thanks for your reply.

Originally Posted by factoryfk For some reason my computer did not enjoy this game at all. When I got to the fire by the bunker it was all choppy (at the start) and went around the corner up the stairs I fell through

Ups, you fell through the the Klong-Building(shown in the screenshot), so i think i use too much fire.

and could see all the guys running around but coulnt shoot them.

The same if we glitch inside of a building that have no interior and normaly can´t be walk in.

My vid card is up to date but who knows lol anyone else have this problem?

As we test the map at first i fell through a ruined platform near the crossroad and i removed some fire until this stops.
But we test the map only with two player. How many player join the map with you?

Dirk

[THOR-LST]

Hi ya freecrac
I agree with factoryfk, we had 7 players in it and map was reel choppy. Im not a map maker but I think there is too much flames that makes the map choppy, we never made it to the second spawn point, everyone one started leaving, was in the map for 50 mins.

[velvet]

Hi Dirk,
I have the same problems with the gfx, played with 3 players and had sometimes a slideshow.
Finishing the map was possible after 2 hours and many deads caused of slow reaction on mouse commands.
My system: Dualcore CPU with 3,3 GHz, 4GB Ram, Nvidia GTS 250 1GB DDR3.
I'm not a mapmaker, but I think some routines for calculating gfx uses the CPU instead the GPU, but as a generally problem of the gameengine itself.

Greetings Olaf

[freecrac]

Hello THOR-LST, hello velvet(Olaf) many thanks for your replies.

With your helps i recognize now that there is a big problem to play the map.

Finally i also think that i have still set too much flames. But along we are testing the map we became no slideshow and our reaction of the mouse was not slow.
We properly finished the map with two player within ca. 40 minutes.

Our systems for testing the map using a LAN-connection:
Intel-Quadcore 2,8 ghz, 4GB Ram, one Nvidia GTX295-card using widescreen 1920x1200 (VSync on), JoOp-Version 1.7.1.9
Intel Dualcore 3 ghz, 4GB Ram, two ATI 4670-cards using widescreen 1680x1050, JoOp-Version 1.7.1.9

Yesterday i have played the map with two other mates via Novaworld and i join into the map at last, so that the other mates had already captured the third LFP(C) before.
One of them told me at the end that this is a hard map, but nothing else.

...

Now i am willing to remove some more flames and send the map again to Wolfseye, so that he can update the map with a newer version.
I hope this solve the problems. I am truly grateful of your help, it is not easy to find a balance between my PC and other slower PCs.

Dirk

[velvet]

Hi again Dirk!
A good idea to "downgrade" the map. I think it will be better to write a hint for system requirements if they are high. If I look at the sysreq the original JO needs and than what machine you have I go a little bit crazy. Not everybody has a modern system or the money to upgrade his computer often. Those people see the requirements, install the game and are really disappointed when they try to play. Others have up-to-date-systems and so no problems. I understand for the mapmaker it is not easy.
Besides: my connections are mixed LAN / WLAN(n) and I have no problems with it.
Greetings Olaf

[Wolfseye]

Originally Posted by freecrac Our systems for testing the map using a LAN-connection: Intel-Quadcore 2,8 ghz, 4GB Ram, one Nvidia GTX295-card using widescreen 1920x1200 (VSync on), JoOp-Version 1.7.1.9 Intel Dualcore 3 ghz, 4GB Ram, two ATI 4670-cards using widescreen 1680x1050, JoOp-Version 1.7.1.9 Dirk

Testing things, if its maps or software e.g. programs, its never good to only do that with kinda more high-end hardware but test it with both, low end and high end hardware.

JO is a old game, a lot of people still play it with older PC's & Hardware, since JO doesn't need High End.

Mappers often forget that when they make maps, that run fine on their Quad Core with 4 GB or more, but create resource problems on older PC's. Always test the map, or ask people to test it for you, on both, low end and high end. That makes sure the map runs best on most peoples computers.

[factoryfk]

It was just me playing , on lan , I dont have the first clue about map making so cant give any sugesstions. but I know you will figure it out. Just trying to help !

[freecrac]

Hello velvet(Olaf),

Originally Posted by velvet Hi again Dirk! A good idea to "downgrade" the map. I think it will be better to write a hint for system requirements if they are high. If I look at the sysreq the original JO needs and than what machine you have I go a little bit crazy. Not everybody has a modern system or the money to upgrade his computer often.

I don´t have the money to upgrade my system often too and i put asides my money many years for upgrading. So i used at the beginning playing JoOp an AMD 1800+(1533mhz) with a Geforce4 Ti4200(64MB) following an AMD 2700+(2166mhz) with an ATI 9800 pro(128MB). I always try a big jump so that i feel the upgrade.

Those people see the requirements, install the game and are really disappointed when they try to play. Others have up-to-date-systems and so no problems. I understand for the mapmaker it is not easy. Besides: my connections are mixed LAN / WLAN(n) and I have no problems with it. Greetings Olaf

Yes for me it is not easy to determine the system requirements for a map.

Dirk