Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hijack The Truck escort will no longer pursue player #140

Closed
alphaTECH-Aus opened this issue Jun 30, 2021 · 7 comments
Closed

Hijack The Truck escort will no longer pursue player #140

alphaTECH-Aus opened this issue Jun 30, 2021 · 7 comments
Labels
bug Something isn't working

Comments

@alphaTECH-Aus
Copy link

Describe the bug
This mission and the escort was working fine some days ago. I've been playing it again today, and the escort will not pursue. It is behaving like a cop in a tunnel in OG Driver 2. The issue persists even after restarting REDRIVER 2.

To Reproduce
I don't know how I've caused this mission to be permabugged.

Expected behavior
The escort should aggressively pursue the player car.

Video
https://youtu.be/HjmP275CGRw

Environment and game (please complete the following information):

  • Game version: 7.2, beta 3
  • Operating System: Windows 10, build 1909
  • CPU model: AMD Ryzen 7 3700X
  • GPU model: Nvidia GeForce RTX 2070 Super

Additional context
My next troubleshooting step is to delete the config files, but first I'm offering up a bug hunt. Recent log file attached, however I do not know if it will be any help since the game does not error or crash.

@alphaTECH-Aus alphaTECH-Aus added the bug Something isn't working label Jun 30, 2021
@SoapyMan
Copy link
Contributor

From what I know this is a purely random bug. Do you use CD image method installation?

@alphaTECH-Aus
Copy link
Author

Yes, my image is PAL v1.1; I have installed both discs and run the game from an image of disc 1. In this instance though, it is a permanent bug. Nothing that I have tried is changing the behaviour.

  • Playing a mission in a different city
  • Playing a mission with pursuers in a different city
  • Deleting config.ini
  • Restarting the application
  • Restarting my PC

@SoapyMan
Copy link
Contributor

Can you try old installation method with extracting one of game CD images to see if it's changes?

@alphaTECH-Aus
Copy link
Author

I would rather not, I think that's barking up the wrong tree. This mission was working fine a few days ago and no files have been modified since then (just checked all the dates/times).

What I did just find is that I can no longer change the cop difficulty. Where are the REDRIVER 2 settings stored?

@SoapyMan
Copy link
Contributor

SoapyMan commented Jun 30, 2021

This is probably related to #132 - game for sure have random behaviour when running from ISO9660 image.

I would rather not, I think that's barking up the wrong tree.

This doesn't make sense to me. Why you reported the bug at first place and now doesn't want to assist check if it's pure random? I don't have an ability to check random bugs since I cannot reproduce them - I need exact PC and OS setup.

Additionally you can check artifact build if its running correctly/differently.
https://ci.appveyor.com/project/SoapyMan/redriver2-10jm8/builds/39791938/job/5k97fxj5uh13v8jq/artifacts

@alphaTECH-Aus
Copy link
Author

alphaTECH-Aus commented Jun 30, 2021

This doesn't make sense to me. Why you reported the bug at first place and now doesn't want to assist check if it's pure random?

My issue is the expenditure of time when I know and can prove that no program files have been changed thus it cannot be a problem with the installation. Further to that, I am not using an ISO 9660 image, it is a Mode 2 (2352) image.

Regardless, I've found the issue. config.dat had become corrupt. I've attached the bad file. I have tested Hijack The Truck with a fresh config.dat and the pursuer is doing its thing again.

@SoapyMan
Copy link
Contributor

SoapyMan commented Jun 30, 2021

It still doesn't mean that it isn't related to me as a programmer since i've seen lots of memory access corruptions related to issue #132. Also #139 fixes some critical write bugs in pathfinding (buffer overruns on writes) so it can be pretty related too and it could have overwritten the difficulty level setup (gCopDifficultyLevel should be at 0..2, was 3 in xconfig.dat)

Glad it's been resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants