I have been playing around with OR for a couple of weeks on my Vista laptop with integrated graphics. See specs below. I wonder how those specs impact these issues:
I have only marginal improvement in frame rates over MSTS. Goes from 18-20 in some heavily scenicked areas to 23-24.
I have a very annoying stutter on every route I've tried. The sim comes to a momentary (one or two-tenths of a second) stop every two to three seconds, then skips ahead to where it would have been without the stutter. The fps counter shows no change in frame rates when the stutter occurs.
On several self-created routes, I have numerous items of vegetation that have their default MSTS .s and .ace file names but have been altered for more realism. I started this years ago when I got some better looking vegetation and proceeded to replace the default trees in existing self-created routes, and I then just imported the revised vegetation with the default names to newer routes. OR gives me the default shapes and aces, such that it is far from the intended appearance.
I had an issue with an activity on the 3DTS Cajon pass with a standoff at a siding. I wondered if OR would handle it better. Nope...I got no approach signal and barreled into a siding at 60+ and then out the other end on green. A few minutes later I had a head-on with a AI train. This particular meet worked fine in MSTS.
Now a favorable issue...the last route I built was a 170-mile extension of my Tallahassee Sub all the way across the Florida panhandle to Pensacola. It was by far the best of my four completed self-created routes. I built it on an XP computer (which is currently inoperable, likely power supply issue). I thought it was done and ready for upload, but when I sent it out last year for testing, everyone with Vista or Win 7 reported freeze crashes at tile boundaries within a few minutes of starting, no matter where on the route. I reproduced the effect on my Vista laptop and spent several weeks working with files, removing interactives and sound sources, and exploring all possibilities I could think of. When I couldn't find the problem or a solution, I pretty much gave up on the route and MSTS in general for quite a while. But the same route does NOT freeze or crash in OR...it appears that the entire route can be run in OR, though with the stutter and vegetation issues, it's not really tolerable. So does this tell any OR or computer vets anything about what the original freeze/crash problem might have been?
And can anyone shed light on the stutter/vegetation/activity issues mentioned? I'm suspecting integrated graphics are the problem. If the laptop doesn't do Run8 well, I will likely be upgrading. And I will continue checking on OR development and wish the team all the best.
Intel Core2 Duo CPU P8600 @ 2.4 GHz
4 gig RAM
Vista Home Premium
Graphics Card Manufacturer Powered by ATI
Graphics Chipset ATI Mobility Radeon HD 3650
Graphics Bus Capability PCI Express 2.0
Maximum Bus Setting PCI Express 2.0 x16
Memory Size 2287 MB
Memory Type HyperMemory
Core Clock in MHz 450 MHz
Memory Clock in MHz 600 MHz
I have only marginal improvement in frame rates over MSTS. Goes from 18-20 in some heavily scenicked areas to 23-24.
I have a very annoying stutter on every route I've tried. The sim comes to a momentary (one or two-tenths of a second) stop every two to three seconds, then skips ahead to where it would have been without the stutter. The fps counter shows no change in frame rates when the stutter occurs.
On several self-created routes, I have numerous items of vegetation that have their default MSTS .s and .ace file names but have been altered for more realism. I started this years ago when I got some better looking vegetation and proceeded to replace the default trees in existing self-created routes, and I then just imported the revised vegetation with the default names to newer routes. OR gives me the default shapes and aces, such that it is far from the intended appearance.
I had an issue with an activity on the 3DTS Cajon pass with a standoff at a siding. I wondered if OR would handle it better. Nope...I got no approach signal and barreled into a siding at 60+ and then out the other end on green. A few minutes later I had a head-on with a AI train. This particular meet worked fine in MSTS.
Now a favorable issue...the last route I built was a 170-mile extension of my Tallahassee Sub all the way across the Florida panhandle to Pensacola. It was by far the best of my four completed self-created routes. I built it on an XP computer (which is currently inoperable, likely power supply issue). I thought it was done and ready for upload, but when I sent it out last year for testing, everyone with Vista or Win 7 reported freeze crashes at tile boundaries within a few minutes of starting, no matter where on the route. I reproduced the effect on my Vista laptop and spent several weeks working with files, removing interactives and sound sources, and exploring all possibilities I could think of. When I couldn't find the problem or a solution, I pretty much gave up on the route and MSTS in general for quite a while. But the same route does NOT freeze or crash in OR...it appears that the entire route can be run in OR, though with the stutter and vegetation issues, it's not really tolerable. So does this tell any OR or computer vets anything about what the original freeze/crash problem might have been?
And can anyone shed light on the stutter/vegetation/activity issues mentioned? I'm suspecting integrated graphics are the problem. If the laptop doesn't do Run8 well, I will likely be upgrading. And I will continue checking on OR development and wish the team all the best.
Intel Core2 Duo CPU P8600 @ 2.4 GHz
4 gig RAM
Vista Home Premium
Graphics Card Manufacturer Powered by ATI
Graphics Chipset ATI Mobility Radeon HD 3650
Graphics Bus Capability PCI Express 2.0
Maximum Bus Setting PCI Express 2.0 x16
Memory Size 2287 MB
Memory Type HyperMemory
Core Clock in MHz 450 MHz
Memory Clock in MHz 600 MHz
Comment