I've been playing Odyssey on PC since it came out. I've used the same graphics card, an EVGA RTX 2060 KO, and it's worked reasonably well, improving performance as Odyssey has been updated. I've always run two monitors, one acting as my browsing monitor always in 1920x1080, and the other "monitor" is my Samsung 65" TV, varying between 1920x1080 and 3840x2160 4k modes as I adjusted to the Odyssey updates. The RTX 2060 ran both monitors at all times. This is a very stable Win10 Xeon PC and I am a 20+ year troubleshooting and systems design veteran.
Last week, I added a second graphics card, an Nvidia T400 (a new low-end Nvidia Quadro class card) to my system. I did this so the RTX 2060 would only need to support the single main TV/monitor and not both monitors. I have little need for advanced graphics capabilities on my browsing monitor and the Nvidia T400 is less than a year old release card and affordable (yes, an affordable new Nvidia card! LOL) I had zero PC problems with the installation of the cards and I'm using the GeForce gaming drivers rather than the Quadro drivers. When Odyssey initially launched after my card addition, it decided to use the T400 on my smaller monitor. It took several minutes to launch. The option to change the display in the graphics settings is now grayed out and unselectable. I then shut down the game, manually edited the graphics start file to use card "1" instead of card "0". Odyssey then launched properly on the larger monitor. To be painfully clear, the RTX 2060 is ONLY physically connected to the larger 4k monitor and the T400 ONLY to the smaller 1080p monitor.
Here's the problem. Prior to the T400 being installed, using only the RTX 2060 running both monitors, my Odyssey startup time was around a minute or less. After installing the T400 and manually editing the graphics file to tell the game to use the second monitor (changed from '0' to '1' monitor), it continues to take a very long time to load. Based on the time to load and behavior, I believe Odyssey is using the T400 card for the initial load, planet generation, etc, then (probably) reading the user-accessible config file and only then switching and running the game correctly on the RTX 2060. Using the highest graphics quality settings for 1080p (1920x1080), I now get consistent 60fps with occasional fps drops to around 55fps (and extremely low fps during loading screens which is another subject entirely that bothers me, but not directly related to this issue). I chose the Nvidia T400 deliberately because both the T400 and the RTX 2060 use the same Turing core and can therefore use the same graphics drivers. I don't expect the T400 to provide any enhanced performance, but I do expect the RTX 2060 to work as well or better than before.
Why is Odyssey using the T400 for launch prior to switching to the RTX 2060 for gameplay and how can that be changed?
Why is my ability to change my video card (and therefore monitor), greyed out in the graphics options of the game? When using one GPU and two monitors, this option is NOT greyed out. This option is therefore inherently labelled incorrectly - it appears to be a choice of video cards while it is in fact a choice only of the screen the came is displayed on.
Why is the T400 being used at all by the game? There MUST be another setting within Odyssey's startup profile that I haven't found yet. My first guess is Odyssey has a default launch state to use the default/primary GPU in the system before reading the individualized config files. This is a practice I need to be able to adjust.
How can I have Odyssey completely ignore the T400, even during startup, and strictly use the RTX 2060 as my config file tells it to do?
Where is the "secret" or embedded startup settings? This is not the only issue I've had with those, but the most noticable because I don't like waiting up to five minutes for a game to load with a robust system. The existence of a "secret" or embedded startup settings is also apparent in the way the bindings are assigned, either by PUID or by "name". I admit there is a chance there is a Win10 default setting Odyssey is initially referencing, but that is obviously unreliable with both graphic settings and with binding identification (the whole bindings issues are, again, another separate topic, but a sore point for me.) As a former developer, this indicates a very "slack" (I'm trying to be nice) way of encoding the loader prior to invoking the user-defined presets. Only the "first" bootstrap load of the game should rely on this, not the entirety of the load prior to opening and making changes to the user-defined settings. This should occur MUCH sooner in the game's initialization process.
Frontier/Fdev - this is an example of a core issue with the game that causes frustrations for so many players. Even a novice can see the startup/initialization routine is an independent operation from the actual game engine and I see no reason a simple startup/initialization routine can't be optimized in a very short time. I suggest these initial hidden settings be exposed for editing as a very straightforward and fast solution for advanced users. Computers are not so heterogenous that the current initialization routine is a good solution and this is tacitly confirmed with the addition of the existing user-accessible customization config files. This is also an issue that can only become more problematic over time as the operating systems and computers change because the static default hidden configs will need to change as well. If that's already made available, please use it in the proper place so it can be used optimally. This, I suspect, will also give the opportunity to DRASTICALLY reduce complaints about custom bindings! Additionally, enabling access to the initialization procedure of defining available devices (as an "advanced" config of sorts) will also allow players to customize their configurations for very complicated mixes of inputs. Everyone wins with a very short turnaround and cost effective alteration to the intialization.
Please help me find the way to change the behavior, especially the GPU loading routine.
Thanks very much!
Last week, I added a second graphics card, an Nvidia T400 (a new low-end Nvidia Quadro class card) to my system. I did this so the RTX 2060 would only need to support the single main TV/monitor and not both monitors. I have little need for advanced graphics capabilities on my browsing monitor and the Nvidia T400 is less than a year old release card and affordable (yes, an affordable new Nvidia card! LOL) I had zero PC problems with the installation of the cards and I'm using the GeForce gaming drivers rather than the Quadro drivers. When Odyssey initially launched after my card addition, it decided to use the T400 on my smaller monitor. It took several minutes to launch. The option to change the display in the graphics settings is now grayed out and unselectable. I then shut down the game, manually edited the graphics start file to use card "1" instead of card "0". Odyssey then launched properly on the larger monitor. To be painfully clear, the RTX 2060 is ONLY physically connected to the larger 4k monitor and the T400 ONLY to the smaller 1080p monitor.
Here's the problem. Prior to the T400 being installed, using only the RTX 2060 running both monitors, my Odyssey startup time was around a minute or less. After installing the T400 and manually editing the graphics file to tell the game to use the second monitor (changed from '0' to '1' monitor), it continues to take a very long time to load. Based on the time to load and behavior, I believe Odyssey is using the T400 card for the initial load, planet generation, etc, then (probably) reading the user-accessible config file and only then switching and running the game correctly on the RTX 2060. Using the highest graphics quality settings for 1080p (1920x1080), I now get consistent 60fps with occasional fps drops to around 55fps (and extremely low fps during loading screens which is another subject entirely that bothers me, but not directly related to this issue). I chose the Nvidia T400 deliberately because both the T400 and the RTX 2060 use the same Turing core and can therefore use the same graphics drivers. I don't expect the T400 to provide any enhanced performance, but I do expect the RTX 2060 to work as well or better than before.
Why is Odyssey using the T400 for launch prior to switching to the RTX 2060 for gameplay and how can that be changed?
Why is my ability to change my video card (and therefore monitor), greyed out in the graphics options of the game? When using one GPU and two monitors, this option is NOT greyed out. This option is therefore inherently labelled incorrectly - it appears to be a choice of video cards while it is in fact a choice only of the screen the came is displayed on.
Why is the T400 being used at all by the game? There MUST be another setting within Odyssey's startup profile that I haven't found yet. My first guess is Odyssey has a default launch state to use the default/primary GPU in the system before reading the individualized config files. This is a practice I need to be able to adjust.
How can I have Odyssey completely ignore the T400, even during startup, and strictly use the RTX 2060 as my config file tells it to do?
Where is the "secret" or embedded startup settings? This is not the only issue I've had with those, but the most noticable because I don't like waiting up to five minutes for a game to load with a robust system. The existence of a "secret" or embedded startup settings is also apparent in the way the bindings are assigned, either by PUID or by "name". I admit there is a chance there is a Win10 default setting Odyssey is initially referencing, but that is obviously unreliable with both graphic settings and with binding identification (the whole bindings issues are, again, another separate topic, but a sore point for me.) As a former developer, this indicates a very "slack" (I'm trying to be nice) way of encoding the loader prior to invoking the user-defined presets. Only the "first" bootstrap load of the game should rely on this, not the entirety of the load prior to opening and making changes to the user-defined settings. This should occur MUCH sooner in the game's initialization process.
Frontier/Fdev - this is an example of a core issue with the game that causes frustrations for so many players. Even a novice can see the startup/initialization routine is an independent operation from the actual game engine and I see no reason a simple startup/initialization routine can't be optimized in a very short time. I suggest these initial hidden settings be exposed for editing as a very straightforward and fast solution for advanced users. Computers are not so heterogenous that the current initialization routine is a good solution and this is tacitly confirmed with the addition of the existing user-accessible customization config files. This is also an issue that can only become more problematic over time as the operating systems and computers change because the static default hidden configs will need to change as well. If that's already made available, please use it in the proper place so it can be used optimally. This, I suspect, will also give the opportunity to DRASTICALLY reduce complaints about custom bindings! Additionally, enabling access to the initialization procedure of defining available devices (as an "advanced" config of sorts) will also allow players to customize their configurations for very complicated mixes of inputs. Everyone wins with a very short turnaround and cost effective alteration to the intialization.
Please help me find the way to change the behavior, especially the GPU loading routine.
Thanks very much!
Last edited:
