Indiana Jones is fun, but damn this game is the biggest technical mess I have ever attempted to play. Everything was fine on the Indiana Jones 1 jungle prequel dream and the Vatican, I was running the game with max settings on everything but texture pool size at 1080p with DLSS Ultra with 60+ fps almost all of the time. As soon as I got to Giza, everything went completely to shit. I get these massive FPS drops when moving around, especially when exiting a cave or building and coming out into the sunlight, but also at other times. I've lowered every graphics setting in the game to lowest setting and these framedrops still happen. At first it was just an annoyance and I managed to explore alot of Giza, but now I've just reached an area where I need to transition from one bullwhip swing to a 2nd bullwhip swing and the massive FPS drop happens right while I'm swinging, so the huge additional input latency means I can't aim at the 2nd bullwhip anchor point in time, and have now fallen to my death about 20 times attempting it. I'm really at a loss on what to do here, I've done everything I could find online from disabling DLSS to going into the Nvidia Control Panel and making sure low latency mode was off, still massive framerate drops. I guess I'm going to have to install it on my Series X and pickup from there, thank God for crossplay on Xbox.
One thing is for sure, if Machine is going to keep using this id Tech 7 derived internal engine, they need to get id's engineers to help them get it running better. Not only does the game run like crap on PC even 2 months after release, but there are all kinds of graphical issues on the Giza map such as checkerboard artifacts, pop-in, and lots of aliasing, it certainly doesn't look anywhere near as good as Doom Eternal or the earlier jungle and Vatican maps. I think they bit off more than they could chew attempting to make a map this size in id tech.
EDit: Ok, I just realized that my Nvidia app automatic driver downloads got turned off at some point and I don't have the latest drivers, downloading those now to see if that fixes the issue.
Last edited by shikamaru317 - on 12 February 2025








