Solution to texture glitch in the tunnel section of "Victor Charlie"

[Don't shoot me 0_0]

Find your config.cfg
and locate the following lines:

seta r_allow_intz "1"
seta r_allow_null_rt "1"

change them to:

seta r_allow_intz "0"
seta r_allow_null_rt "0"

Found on a Call of Duty forum in China, haven't tried it myself. I'll let you guys know if this works.

Tested valid and effective. See screenshots below:

http://steamcommunity.com/sharedfiles/filedetails/?id=785679041
http://steamcommunity.com/sharedfiles/filedetails/?id=785679024
http://steamcommunity.com/sharedfiles/filedetails/?id=785679012

*edited Sep 13, 2022, dont set config.cfg as read only, otherwise it might corrupt your save files*

[Don't shoot me 0_0]

If this helped please gimme feedback

[HUjARK]

Yes, thank you!

[HoldOnToYoButts]

IT WORKED THANK YOU SOOOO MUCH

RIP Billy btw(

[Fatality]

It worked for me
thanks

[Caesar]

This might on my part of being an idiot but I tried your solution and I clicked the read-only option on the properties of the files and now my game doesn't save properly and everytime I close the game it goes back to the save spot I changed the files on.

[Billy]

Nice. THX!

[Хадарыч]

Thank you very much!

[raJze_R]

Thanks it worked

[lewosch]

Originally posted by odeghy:

While this does fix the texture glitch, it also causes a much, MUCH bigger problem.

Basically, I kept playing the game until the second-to-last mission, saved and quit. I just returned now to find the game didn't save any of my progress.

Whenever I go to resume it just puts me back in the tunnels where I encountered this glitch.

I believe campaign progress in this game is saved inside the config files, whereas in some older CoDs (4 and WaW, for example), there were separate save game files outside of configs...

long story short; the reason is probably setting the config as read-only after doing the tweak. actually, I think the fix should still work anyway without setting anything as read-only, once you edit the required command lines and then save changes made to the file.

[Agent BidOofers]

Just a quick question, will this also change that moment in "Vorkuta" where the same bug happens? That moment being the brief cutscene with Reznov, Mason, Sergei, and tons of other prisoners on the lift?

[lewosch]

Originally posted by Dr. Oofers:

Just a quick question, will this also change that moment in "Vorkuta" where the same bug happens? That moment being the brief cutscene with Reznov, Mason, Sergei, and tons of other prisoners on the lift?

not entirely sure as I haven't personally encountered this glitch, but I guess the answer should be "yes".

[Agent BidOofers]

Originally posted by lewosch:

Originally posted by Dr. Oofers:

Just a quick question, will this also change that moment in "Vorkuta" where the same bug happens? That moment being the brief cutscene with Reznov, Mason, Sergei, and tons of other prisoners on the lift?

not entirely sure as I haven't personally encountered this glitch, but I guess the answer should be "yes".

Just reached this part again during my veteran (all intel) run. It's fixed! Thanks!

[Grimble]

It worked just fine! Thank You!!!

By the way, don't set the file as read only. Otherwise you won't be able to save your progress

[Axvill]

Thank you!

[Bob, El Deconstructor]

It worked for the whole moments when having this issue. Thank you!