Tale of Two Games

Matrix Games Forums

Forums Register Login Photo Gallery Member List Search Calendars FAQ

My Profile Inbox Address Book My Subscription My Forums Log Out

Tale of Two Games

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [New Releases from Matrix Games] >> Tigers on the Hunt >> Tech Support >> Tale of Two Games

Page: [1]

Message

<< Older Topic Newer Topic >>

Tale of Two Games - 1/5/2019 3:35:45 PM

dave68124

Posts: 24
Joined: 3/29/2016
Status: offline

Played two different scenarios with the 1.20B patch running. One scenario - Knock em Down is a massive scenario with a lot of space and units. The game ran just fine.

Played the first RB scenario from Rico, One down, Two to go and the game grinded to a halt and made the scenario unplayable. Pulled out the watch and seemed to average about 20 seconds per move of a unit. The game is about a quarter of the first game.

I rebooted between the games and ran Razor while playing. I am perplexed why a larger game would run fine and another game that is smaller in terms of space and units would be virtually unplayable.

Running Windows 10 Pro, I7 @2.70 GHz, RAM is 32GB, Virtual memory (without Razor) is 63.9 GB, Video card is a Geforce GTX 780M.

Really appreciate the efforts to streamline the game speed with the patches, but gut feel is that 1.18 and earlier patches ran much better than the 1.20 patch. Maybe there was nothing done to impact the 1.20 patch, but if I could go back to 1.18 where the game seemed to run a lot smoother, I would. Hope this information helps as you streamline the code.

Post #: 1

RE: Tale of Two Games - 1/5/2019 3:49:24 PM

Peter Fisla

Posts: 2503
Joined: 10/5/2001
From: Canada
Status: offline

quote:

ORIGINAL: dave68124

Played two different scenarios with the 1.20B patch running. One scenario - Knock em Down is a massive scenario with a lot of space and units. The game ran just fine.

Played the first RB scenario from Rico, One down, Two to go and the game grinded to a halt and made the scenario unplayable. Pulled out the watch and seemed to average about 20 seconds per move of a unit. The game is about a quarter of the first game.

I rebooted between the games and ran Razor while playing. I am perplexed why a larger game would run fine and another game that is smaller in terms of space and units would be virtually unplayable.

Running Windows 10 Pro, I7 @2.70 GHz, RAM is 32GB, Virtual memory (without Razor) is 63.9 GB, Video card is a Geforce GTX 780M.

Really appreciate the efforts to streamline the game speed with the patches, but gut feel is that 1.18 and earlier patches ran much better than the 1.20 patch. Maybe there was nothing done to impact the 1.20 patch, but if I could go back to 1.18 where the game seemed to run a lot smoother, I would. Hope this information helps as you streamline the code.

Hi Dave, with 1.18 patch I was trying to improve the LOS processing speed. However, in the end my improvement feature compromised some important LOS features so I had to disable this functionality for now. So 1.20 is essentially the same before 1.18 patch and restored quality LOS processing functionality. I will look into improving LOS processing in the future.

(in reply to dave68124)

Post #: 2