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
Scenary Quality / Density
Not verifying game cache
Backing up the game
In my opinion verifying your game cache does work in some cases because it reinstalls all corrupt/missing files and fixes them.
Presumably the spec's of the PC haven't changed and you would have noticed if a memory module had stopped working. Could there be some task running in the background hoovering up masses of memory?
Are you sure your Radeon Settings are allowing TS2017 graphics settings to control your GPU and not the other way around? Have that round the wrong way and it is possible to get all sorts of graphics issues.
In your Radeon Settings Game Profile for TS2017, make sure 'Application Controlled' is set in 'all' drop down boxes that give you that as a choice. Leave the others as they are.
Also make sure your Radeon drivers are up to date 'first', there have been a number of up dates over the last few months.
Best.
Sheesh... as much as I hate AMD FX line, FX-8350 is NOT a weak CPU, not for the purposes of this game.
And R9 390 is plain overkill.
OK, we are missing few points of critical info here - what is the storage of the computer, HDD, SSD etc.?
Is immediate reloading helping or not?
Have you tried cleaning the blueprint cache (see manual)?
1. SSD: Transcend MTS800, M.2 2280, 256GB, SATA III, MLC (TS256GMTS800/256GB SATAIII 2280) - http://www.transcend-info.com/Embedded/Products/No-645
2. HDD: SEAGATE - ST1000DM003-1ER162 ATA Device (1 TB, 7200 RPM, SATA-III)
The OP's R9 390 GPU is not overkill chap, it is ideal if he wants to play modern games and TS2017 at higher settings and FHD or a bit higher.
Sheesh... but regards anyway.
Your drives appear fine. Do you have any background programs running at the same time as TS2017?
Best.
Ok, so we can rule out hardware issue pretty safely.
So, here is what to do:
delete the blueprint cache (from within the game, it is somewhere in the settings) and if this does not help:
move you entire Railworks folder elsewhere (or delete it) and do a clean redownload of everything
OK, this issue is clearly software related, given the fact, that TS2017 works on much weaker machines.
R9 390 8GB is an overkill for TS2017, TS2017 GPU memory utilization is maxing out somewhere between 1 - 2 GB in FullHD - and as a matter of fact, this would not be the first time in history, when more is actually less (there IS a thing like a "too much memory error", no one likes to admit that, but I have seen repeatedly similar error over the years, both in DOS and Windows alike, both main RAM and GPU RAM alike).
Also can not fully agree on that updating the drivers will help - I am not sure about that, actually older drivers might work better (on the other hand, given the fact, that Windows 10 likes to replace everything with is own generic drivers, this might by actually worth a shot)
The recent Radeon driver updates over the last few months address a number of issues plus add game performance improvements for some, dependant on game being played. They also add other gaming apps if required or wanted.
I beg to differ based on new build past experience.
TS2017 is not a modern game, it is a game running on decade old and fairly obsolete DirectX 9 engine.
And again, I was talking about FullHD, nothing more, as we were not given anything at all to work with from the OP (maybe I missed something) and I have to base my assumptions on something (I measured memory utilization of TS2017 myself in FullHD in order to know, how much memory is really needed for that resolution - btw. it is not very to extrapolate other thinkable resolutions once we have established a baseline and it is still coming pretty short of those 8GBs).
Anyway, back to the original topic.
This problem is much more likely to be software related and the OP should really exhaust all the software options before he starts meddling with his hardware - that is my point all the time and this is why I went ballistic when I saw your posts going in hardware direction, because the hardware "route of solution" is in this case, well, premature at best and completely misleading at worst.
I do not take kindly to you suggesting that I may be 'misleading' Felix. I have helped many on these forum threads and like today, my help has worked. Proof yet again of my methods.
Regards all the same.
Even the OP thinks, that this problem is not hardware related - and guess what: I agree with him.
Have you even checked his screenshots? I seriously doubt it.
There is problem with missing objects in them and this was never ever related to hardware, but this was always caused by software, usually by some glitch in the configuration or even by some missing assets - there no way to fix this by tinkering with graphics drivers or hardware in general, so please, stop draging this thread in completely wrong direction!
You clearly don't seem to like me helping with my methods of fault finding that work, as they did today for someone else.
I start at the top with PC specs and work down, you want to start at the bottom and work up. That does not always work, as seen many times in these forum threads as everyone can see, where hours and hours of time are spent by others trying to solve a problem, then low and behold, something was missed, or it was a PC spec problem after all when PC specs asked for, finally appear.
Steam 'System Information' PC specs don't just reveal hardware, they reveal how that PC is put together and OS being used, vital information before starting any type of fault finding.
Do you go to the garage with an engine problem and the mechanic suggests that changing your tyres is the first thing you should try to fix the fault? Of course he won't say that.
He will say lift your bonnet and lets take a look at your engine first for examination. Only then, will he look at any engine management software that 'may' be faulty if the engine appears ok.
That is how I work Felix, I will not ever change that approach, it is logical and works very well indeed for me over the years, as others on this forum know well too.
Start at the top first and only then work down, then you don't miss something important. That is all I am doing chap.
At no point have I suggested this is just a hardware fault Felix, so please don't make out I have.
I have suggested a few things to the OP to check, but he has not confirmed, as yet, that he has checked those things. So we are both not able to solve the problem at the moment.
And this is what exactly then?
You have hijacked a software issue and coverted it to a hardware one - play with words as much you can, there is no way around this.
Also, from you aswer, I take it that you never bothered to check those screenshots. You should have, because the OPs description of the problem is somewhat inaccurate, these are not missing textures, these are missing 3D objects.
And there is no way, NO WAY AT ALL, anything you wrote has any impact on that issue.
The reason I was asking the OP about storage was simple - it is known, that TS2017, when stored on really slow drive, can produce similar graphical glitches - but incidentally, storage was the only component you never mentioned.
The OP was asked about his computer for one reason only - to rule out that we are dealing with yet another low power / low specs system, nothing more - and once it was clear, that this is not the case, it was time to move on, in order to try some real solution, like deleting blueprint cache, verifying the game files and, in the end, complete clean install of the game itself.