Anomaly Research in Yanov Quest GLITCH

[hakuBirb]

Hello Call of Pripyat Community,

I have been a long time fan of this series and have played the first two way back when they were coming out back when they were CDs in best buy. I have yet to play Call of Pripyat until now.

I carelessly ran into what seems to be a very easy issue to fall into: I put the sensors in the wrong anomalies for the Anomaly Research quest. What is worse, because I was doing a run to blanket a bunch of quests all at once, I sped through it not knowing what I did with the intention of coming back much later to finish it... Now, a day and many hours later, I come back to it and I realize what I have done.

I can backtrack and lose a crazy amount of progress (I did the quest near when I first came to yanov... i've now finished nearly all quests in both the first and second area now)

Or, if anyone in the community knows a workaround? I will be willing to spawn in items (more sensors), kill and restart the quest, memory edits, whatever that might be done to fix this issue, whatever the tedium, WITHOUT backtracking.

If this is possible, please let me know,

Thank you!

[arottweiler]

I've heard of this issue before but it's never happend to me and I can't see how it's possible. What is the issue with the mission? Did you place scanners at anomalies that were not part of the missions so you have more anomalies marked on the map to place scanners but don't have any left? Have you checked with the technician at the Scientist bunker to see if he has any more to give you?

If you just need more scanners to complete the mission I think there's a way to spawn them so will try to find out how to do it.

[terryt3535]

Interesting idea to spawn new detectors. The game is old enough now that a bunch of possible references have disappeared. Assuming it's possible, I don't know enough about console commands in Stalker to spawn a new set. The most active site for people with "developers" knowlege is http://themiserymod.com/index.php, but it's been a couple of months since they updated the site. Another place to ask is http://modddb.com/forum/

I would say to bite the bullet and load an earlier save.

[terryt3535]

Found a video to enable the debug menu, but it's for the Mod Call of Chernobyl, not the base game. CoC supposedly runs on the same version of the .EXE as CoP, so it could help.
https://youtu.be/kXCHwm0YxIo

[arottweiler]

I'm running the debug spawner and I think it's compatible with vanilla CoP and all mods and is just a case of enabling it in the file below. If it doesn't exist there is no harm in creating it.

gamedata\configs\debug\xrs_debug_tools.ltx

Change the value:

enable = False

to

enable = true

and the debug menu should be enabled.To test it press the ESC key ingame to pause the game and then the S key. The Debug menu should appear.

In the spawn menu try typing this which is the only scanner reference I could find in the items list:

jup_b209_monster_scanner

I just spawned one and it looks like the same scanner issued by Sakharov so it might help complete the mission but I agree it's probably easier to go back to the last save as you'll get through it in half the time.

[hakuBirb]

Thank you for the info and replies.

I wonder if there is a command or a way to simply force the quest to finish, and just progress to the next quest. I usually don't like to do things like that, but for the sake of continuity.

arottweiler,
now that I know this is an issue, it is hard for it to happen again. The problem is, the game lets you place the scanner at any anomaly you want. If you look at your pda map, it will mark the right ones, but if you are running about and you're just looking at the radar map at the top, it will actually show a marker to place a scanner in any anomaly in yanov. I just happened to be clearing many quests all at once and was not paying close attention to it to realize that. The place i'm at now, the quest wants me to place a scanner at the bitumen anomaly but I have already placed all of my scanners at other anomalies.

Thanks for the .ltx and the console commands, I'm definitely going to try that out next time I start up the game. I just hope that I can finish the quest that comes right after, the one where you need to place 2 more scanners.


terryt3535,
I took a peek at some other similar sites, I haven't checked moddb, and I noticed the same, many of them are slow or outdated. I figured i'd try the steam community first. If anything, i'm probably going to stick with the solutions here as well. I do have the ultimate option of just rolling back the saves.

I am running vanilla (gonna run mods after I beat it once) and the big reason why I don't want to roll back is because it was done so so long ago. So long ago that i'd have to say i'd lose half of my total gameplay. It was literally the first thing I did when I went to Yanov and since i've placed them, I completed nearly all of the first area and Yanov. It is a lot of progress and a lot of time.

In the past, especially back when I was playing these older games on older machines, losses like this were much more common. However, no matter the case, no one likes to lose 5+ hours of gameplay if there may be some hope of another option.

If worse comes to worse, and I cannot find a solution, yes, I will roll back. If anything, I will know how to progress faster and better, it will just be tedious.

I'll keep you updated for when I try the debug fixes.

[terryt3535]

Good luck Stalker.

[arottweiler]

If this is your first playthrough CoP then please don't use the degug utility. I beg you lol

I play missions in a similar way and will line up a few to do in one go and then get back to the Skadosvk feeling smug but there have been times I've messed up and lost hours of progress. When I replay it I find I can do it all again in a fraction of the time so no matter how long you think it will take you the right option for the logevity of CoP is to replay it. Unless you know you can spawn the scanners to complete the mission and not use it for anything else but that would be a tall order.

[Drazial - UK]

For anyone in the future who enabled the debug menu to spawn in replacement scanners: jup_b32_scanner_device is the correct device to spawn rather than the previously mentioned one. Cheers!