build r (18371)
build r (18371)
testing the 32bit version again today on the largest maps and races
another day another test, and another desktop shortcuts that's altered after a patch update, as i have mentioned before if you make your own, eg 32bit or 64bit, once it's been updated, they revert back to 32bit ones for some reason, so if you don'y know or look, it alters it without you realizing it.Re: build r (18371)
settings same as 64bit test
Re: build r (18371)
in menu's before starting a game baseline view
Re: build r (18371)
36 seconds to make game and load into first screen in game
seems at times that the 32bit version can be lower, but the amount of lines in the running of this version is more up and down, where as on the 64bit version the line was almost fixed and steady on the graphRe: build r (18371)
as shown on this screen
Re: build r (18371)
Thanks for your testing. I haven't really had time to put the large maps through their paces, so this information is very useful to us.
I did run into an issue a little while back where I had created a separate development shortcut with a "-noupdate" switch, and somewhere along the line Win10 decided that it would use that command switch for all versions of every shortcut that launched the same executable. It was irritating, but it was Win10 stupidness and nothing to do with us. I apologize for the inconvenience, but since actual customers are going to be launching the game through Steam, this is not something we can afford to spend a lot of time on trying to fix. If you have some ideas on what might be causing this, I'd love to hear them.
I use desktop shortcuts to run the 64-bit client as well, and I haven't run into this problem. As you can probably guess, our update client doesn't have any desire (or power) to change your desktop shortcuts, nor do we change the names or locations of the executables.zakblood wrote:another day another test, and another desktop shortcuts that's altered after a patch update, as i have mentioned before if you make your own, eg 32bit or 64bit, once it's been updated, they revert back to 32bit ones for some reason, so if you don'y know or look, it alters it without you realizing it.
I did run into an issue a little while back where I had created a separate development shortcut with a "-noupdate" switch, and somewhere along the line Win10 decided that it would use that command switch for all versions of every shortcut that launched the same executable. It was irritating, but it was Win10 stupidness and nothing to do with us. I apologize for the inconvenience, but since actual customers are going to be launching the game through Steam, this is not something we can afford to spend a lot of time on trying to fix. If you have some ideas on what might be causing this, I'd love to hear them.
Re: build r (18371)
i only mentioned it as it happens, but like you i now check each update to make sure i'm on the version i wish to be on and test, for me i'd say it's windows 10, as it has happened before, as i run as admin from a admin account, but the shortcut is a manually made one, on a update if the exe changes then it also alters the shorcut, so when a exe it's linked to hasn't been updated, it doesn't, it seems to be how windows 10 works, which is good in one way as it doesn't break the shortcut and re links it to the game exe, but not always the one you had, if you use the 32bit version, it never alters that either, as iv'e tested that a few times on the updates as well, so it seems maybe you have updated the 64bit exe a few times, where as the 32bit exe doesn't matter if it gets updated or not, as that's the default one i'd guess at?
if this is makes sense
if this is makes sense

Re: build r (18371)
no results today as both games started and both too rushed and had food problems too early and never recovered so abandoned both, will start another one tonight or tomorrow 

Re: build r (18371)
1572 uploaded, to nights test which i will mid game tomorrow and end test by the end of the day and post results and findings
Who is online
Users browsing this forum: No registered users and 2 guests