Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
6 
Report this post
First off, let me ask, did you install the brand new Adrenalin 2020 driver from AMD that JUST came out? Like, yesterday? (At the time I'm writing this.) Because I wouldn't be surprised if this driver is going to be glitchy at the start. AMD completely overhauled their driver, with this release. Especially for the new 5xxx/Navi/RDNA cards.
I haven't had a chance to install the Adrenalin 2020 driver yet. I also don't have one of the latest AMD cards. (I do have an RX 570 Polaris/GCN GPU in an older system. So I can still install this Adrenalin 2020 driver, and give it a go when I have some time.)
There's something you can try, though.
I can't tell for sure if you're using anti-aliasing with TRON 2.0. Your screenshot has been downsized too much, for me to know for certain. But if you are, make sure you're not using Adaptive anti-aliasing. This can make objects "disappear" in the game. It's a known issue with AMD cards in TRON 2.0. Has nothing to do with the mod.
Visit this page on AMD's site, and scroll down until you see Adaptive anti-aliasing/multisampling.
https://www.amd.com/en/support/kb/faq/dh-012
Select a different type of anti-aliasing than Adaptive. In both the Global Settings, and the specific game Profile for TRON 2.0.
If you're using the Adrenalin 2020 driver, AMD completely changed the interface and it won't look like the screenshots on that page. (I'll have to install it myself, in order to see how things have been altered.)
Other than that, I'm not sure why the Light Cycle is partially "invisible". Again, it could be the driver, and AMD needs to update it.
I do not have that driver installed. Actually just got this card a few weeks ago. I'm showing that the Radeon Software Version I have installed is 19.11.3 and the Radeon Software Edition is listed as Adrenalin 2019. Both the global and Tron 2.0 anti-aliasing settings have anti-aliasing set to Multisampling. Here's a screenshot of my Radeon settings for Tron 2.0: https://gyazo.com/901dc93eef1fe02f2a290aae2d175af6
Additionally, the setting for Frame Rate Target Control is set to Disabled, it was cut off from the screenshot. The only setting that I've actually changed on the card up to this point has been the Virtual Super Resolution, but I have since returned that setting to its default value of Off.
Really appreciate your assistance with this!
Change it, in both the Global settings and the TRON 2.0 game Profile settings. Change them to standard Multisampling (click Anti-aliasing Method, select the item above Adaptive Mutlisampling). See if that helps.
Ah, didn't even see that. I went ahead and changed it to standard Multisampling and the issue persisted. After that I tried verifying the game's cache integrity and it looks like I need to do a clean install now as the mod has been uninstalled. However, the issue still persists in the base game, again, only with classic lightcycles, not the Super Lightcycles. I'll report back with my findings post-reinstall. Also going to look into seeing if I need to update my GPU drivers.
EDIT: Welp, on a clean install, I get this on the lightcycle selection menu: https://gyazo.com/3b881fed2bdf90b0b60cab1498cd49cf
The game doesn't seem to recognize this as a valid lightcycle choice, and I can't choose any other options. If I try starting a match, I get the message indicating that the lightcycle I've chosen is not available for that circuit, even if the circuit in question allows all lightcycles (such as the tutorial)
As for the problem you're having right now, the mod added more Light Cycles to the game. You had one of the newly added ones selected for Single Player matches. After removing the mod, you no longer have those extra Light Cycles. So when you run the vanilla, unmodified game, it can't find the extra Light Cycle that was selected.
You'll need to go into your TRON 2.0 folder. The guide below has an animated GIF that shows how to easily find it, using Steam.
https://steamcommunity.com/sharedfiles/filedetails/?id=325088441
Once you're in your TRON 2.0 folder, go into the Profiles folder. If you didn't change the default name of the game profile, it should be Player.txt.
Open that text file in a text editor, like Windows Notepad. (You might need to run the text editor with Administrator privileges, if your Steam game library and game folders are in "C:\Program Files (x86)". Or else you won't be able to save the change you're about to make.)
Search for "CycleShade" (without quotes). You'll see a line where it reads something like "CycleShade = XX" where XX is a number.
Change that number to 0. Now save the edited text file.
Start the game, and you should be able to select Light Cycles again.
If the issue with the "invisible" Light Cycle persists, I suggest you download the latest Adrenalin 2020 driver and install it. Since 5xxx/Navi/RDNA cards are still very new, AMD will be working out the kinks in their driver. Maybe updating will help.
I'm also going to try running TRON 2.0 on my system with the AMD RX 570 card. Even though it's not the same card you have, it is from AMD and I want to see if I can replicate this "invisible" Light Cycle problem.
One thing I can confirm, is that Adaptive anti-aliasing still causes issues. I saw various glitches in the rendering of objects. So it's best not to use that mode of anti-aliasing with TRON 2.0, on any AMD GPU. However, Adaptive anti-aliasing didn't actually affect the classic Light Cycle.
In fact, no matter what settings I chose in the Radeon Settings software: I couldn't replicate the problem you're having with the Light Cycle. It's rendering fine, in my case. No "invisible" Light Cycle. This is with the mod, too.
Now, unfortunately, I don't have an RX 5700 Navi/RDNA card like you do. So, the reason I can't replicate this problem, might be because it's specific to the newer AMD GPUs. I also don't know what version of Windows you're on. I'm guessing probably Windows 10. Meanwhile, my RX 570 is in an old computer running Windows 7. Not sure if that makes a difference. (I also have a newer computer on Windows 10 with an Nvidia GPU, and the Light Cycle is fine there as well.)
There's only one other quick thing I can suggest, and I don't really think it's going to work. But, why not give it a try. With the Radeon Settings window open at the Home tab: Click on Gaming > Click Global Graphics (lower in the window) > Click Advanced (at the bottom of the window) > Scroll down and click on "Perform Reset" beside Reset Shader Cache.
Other than that, it looks like your only solution might be to submit a bug report to AMD. Click the gear icon in the top right of the Radeon Settings window > Click Report Issues Online. Fill out the form, and explain the issue you're having in TRON 2.0. Hopefully, they'll do something about it in a future driver update.
I'll give that a shot, but I think I have an idea of what could be causing the issue. I previously had an NVidia card and while I did uninstall the drivers for it before installing the ones for my new AMD card, it could be that there's still some residual files left over from the NVidia drivers that are causing a conflict. I attempted to play EA's Apex Legends game last night and encountered some strange shader issues with reflective surfaces. I'm going to look into doing a clean wipe of any NVidia drivers on my system and hopefully that will resolve the issue. I'll update in this thread when I have a chance to do so.
The issue I encountered in Apex Legends was due to a bad installation. Origin's repair function (essentially the equivalent of Steam's Verify Integrity of Game Files function) fixed it. This got me thinking that maybe a similar issue is happening with Tron 2.0. My installation is a clean Steam installation of Tron 2.0 without any mods installed. Before launching the game for the first time, I ran the verify integrity of game files function and it came back saying everything was good. I launch the game, no lightcycle textures, as usual. Go back to check the file integrity and one file had to be redownloaded. Checked again, same thing. So it seems like there's an issue with one file being perpetually corrupted in, but I'm not sure how to find more details on this.
A few years ago I had two mechanical hard drives start to fail, back to back. Even though the S.M.A.R.T. monitoring feature said they were still okay. But, clearly they weren't. Because I was experiencing corruption in files. I ended up having to replace them both.
I'm not saying that's what this is, for certain. But repeated corruption in files is one of the symptoms of a failing drive. Though, it could also just be a loose connector on the SATA cable to the drive. (If it's an HDD or SSD, and not an NVMe drive.)
The drive itself is fairly new, and both Apex and Tron 2.0 have another common factor: Both were installed on their respective drives prior to a new OS install on a new HDD. The original HDD with the old OS is no longer in use, so both games had to reassociate files post-OS installation. While Apex works fine, Tron 2.0 consistently fails to re-acquire the one file missing from its installation, at least through Steam, which makes me think that a fresh install from the disc or completely removing all traces of the Steam installation may fix the problem.