regards
Derek
Moderator: Moderators
Probably you don't do anything differently, a lot of it is down to perception and expectations. Your "hardly any stuttering" may be perfectly acceptable to some users and not be considered worthy of comment or complaint, whereas to others it may be horrendous. Until there is an agreed definition of stuttering and a reliable way of measuring it these debates are unlikely to lead very far.StPancras wrote:...I get hardly any stuttering, I run full details, with most options on. So what do I do differently?....
As I understand it, the recent PhysX version released this summer (2.8.4) is fairly significantly faster even when run on the CPU due to using SSE2 instructions. If so there might even be hope for those of us with ATI cards.msmith4000 wrote:Or even better and probably easier to implement, they will be shifting the PhysX engine used by Railworks over to the CUDA based PhysX SDK so that the calculations can be done on the Graphics card watch this space and get ready to buy yourself a NVIDIA graphics card! (Am I correct Derek??)
Not completely true if you value image quality. I usually upgrade every time a new high end video card comes out and without a doubt each newer card has handled higher AA and resolution better than the last. The frame rates have always improved in RailWorks with each new video card.msmith4000 wrote: That is why the game runs the same speed no matter what graphics card you run
Who's struggling? My two i7 gaming setups regularly sit well in the triple digits with RailWorks at 1920x1200/1920x1080, 8x super sample AA/16xAF.even the highest end CPU's struggle to run Railworks

ightenhill wrote: In simple terms if what derek is hinting at is true, then the P element being moved to the card could be a good move..
idiot wrote:Just thought I'd pass this on.
Yes, I have stopped 99% of the stutters in my RW.
I got one of the relatively new Western Digital 10000rpm hard drives.
Read Time is 4.2ms
Write time is 4.7ms.
-----------------------------------------
It was me who posted that originally in RailWorks, it really did get rid of stutters etc, but its not
doing much good in the WCML as I'm getting them in that route, no doubt caused by
the high density of all the items in some of the sections.
Indeed concide I agree if you are running high resolutions 1080p or higher and lots of AA or have a very fast CPU. I have run Railworks on my 1680x1024 monitor and my 1080p TV with 2xAA and noticed no difference with frame rates indicating that the video card has leg room to spare and not the limiting factor. Thats with 8800GTX which I would class as only a little bit better than a current mid range card these days. Your CPU is much faster than my aging Q6600 though, so if you have a fast Core i7 like yourself and a slow video card then the scales would tip and the video card would become the limiting factor, hence you would need a fast vid card too keep up with the CPU. The key is to have a video card that matches the CPU you have, no point having a top end video card and a bottom of the range CPU (or ancient cpu). And vice versa.djt01 wrote:
Not completely true if you value image quality. I usually upgrade every time a new high end video card comes out and without a doubt each newer card has handled higher AA and resolution better than the last. The frame rates have always improved in RailWorks with each new video card.
This is not to say that the game engine RailWorks uses is fully utilizing the GPU either and that fix is going to take more than just a simple patch.
msmith4000 wrote: Indeed concide I agree if you are running high resolutions 1080p or higher and lots of AA or have a very fast CPU. I have run Railworks on my 1680x1024 monitor and my 1080p TV with 2xAA and noticed no difference with frame rates indicating that the video card has leg room to spare and not the limiting factor.
Here’s an example of pretty graphics –Railworks is has pretty graphics but not as near impressive as say Crysis which makes the Railworks graphics look a little basic. I dont think the graphics engine is all that taxing in comparison to the physics calculations the simulator is having to do.
I dont think the graphics engine is all that taxing in comparison to the physics calculations the simulator is having to do.

From what I remember there was an interesting article recently about PhysX and its software drivers re how inefficient they are because of the type of programming level it was written in which does not take into account a lot of CPU instruction sets. Apparently Nvidia is rewriting that side of them sometime soon.ightenhill wrote:
Despite the physx element being rather clumsy the problem is its still being handled bu rather un optimized code stuck in the cpu cycles.. Despite the fact its doing little , that little part is interfering with everything
True, there is a lot that Railworks has to be flexible for.ightenhill wrote:The problem with train sims is that the engine has to involve a rather clumsy asset editor.. In an ideal world we would buy routes where the route is designed from the ground up with efficient design rather than thousands of individual assets being placed on tiles,
Despite the physx element being rather clumsy the problem is its still being handled bu rather un optimized code stuck in the cpu cycles.. Despite the fact its doing little , that little part is interfering with everything