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
It may have something to do with either a) it being an almost direct port from consoles, which use HDMI, or b) the DVI to HDMI adapter, or the DVI to HDMI cable has a pin-out that does not properly convert the signal, as DVI has many more lines than HDMI, so my signal may have lost some kind of key data used by real DVI when it was "adapted" from DVI to HDMI, making my monitor upset :P
lol, no. firstly it's not a "port". the game was originally being developed as a PC exclusive before development pivoted to the xbox.
Also, contrary to popular belief "porting" isn't a bad thing or dirty word either. I don't know about the Forge engine, but Engines like Unreal and Id Tech5 are designed to be highly portable. The big problems with porting usually had to do wth poor design decisions such as not properly reworking control schemes to be more appropriate for PC gaming, or not giving proper graphics and sound options to take better advantage of PC hardware. Fallout 4's 4 response limit (designed to be applied by one of 4 hat switch positions( is often cited as as good example
HDMI and DVI-D are directly electrically compatible. Same video signal, different physical connectors. That's the only difference. You mostly likely just had a bad connection, or a poor quality cable or adapter.
https://www.pcmag.com/encyclopedia/term/60987/hdmi-dvi-compatibility
Well it's definitely not the connection, that is something that not only was troubleshot, but also is outrageously easy to deduce. I'm actually researching it now, but it has something to do with the actual packets sent over the line being lost or corrupted due to the signal being converted twice in a single run, or the GFX card sending a signal intended for the port the cable was plugged into (HDMI), but this was incorrect as the signal ultimately was recieved by a DVI port at the rear of the monitor. HDMI and DVI are essentially identical, with the exception of audio, DVI analog support, DVI being limited to RGB, etc, minor stuff really. I think the error may be related to an inability to properly acquire the monitors EDID (hardware specs) by the GFX card due to all the adapting going on lol. Long story short, all the hardware is in perfect working order physically, however for some reason this one specific game did not like the way my monitor was attached due to some digital error through the line, some specific config in the game, etc. I will be investigating and researching to find the EXACT reason, to the very single iota, for self interest. Anyone who wants to be informed when the actual reason is discovered just leave a reply here or PM me. Thnx for all the help, and happy gaming folks :P