Quote:
Originally Posted by CapnScurvy
The second thought is just how large the 1600x bearing tool image is. It's really a larger file.
Can this make a difference in getting a CTD when a large saved point (a large convoy of ships are trying to be saved) along with the large bearing tool? Could be. The tolerances for any saved game seems to be the amount of memory it takes to render the complete screen over again. It also follows that your system makes a difference too, got a new computer with the latest and biggest video card and tons of memory? You probably won't have a care in the world. Have a mediocre setup, you may have trouble. Just food for thought.
What I should do is make a smaller group of bearing tools that covers only 1500 yards, not 3000 yards. I think that would lower the memory size of the bearing image, allowing for a smaller chance of stretching your system to the limit.
|
You'd think a new rig with an i5 2500K processor, 4GB RAM (with the Large Address patch applied) and an ATi 6950 graphics card would chew SH4 up and spit it out, but unfortunately that is not the case. What truly baffles me is that, when playing v1.4, I'd encounter MUCH larger convoys with barely a hiccup AND with the 3000m Bearing Tool running (42MB per file as opposed to 35MB of the 3000y version).
To add to my confusion, I decided to add the 3000y Bearing Tool to one ship only and see what happens. So I slapped it on a Gato and picked a random Single Mission. A few minutes later I encountered the tell-tale sign of a convoy being picked up - stuttering - and half-expected a CTD. Well, not only did that not happen, but to my amazement I was looking at a convoy 6 times the size of the one that had caused my CTD in the Tokyo Express mission! Gotta love computers
Needless to say, I'm gonna load Tokyo Express with this setup and investigate further.
ETA: Tried the Tokyo Express mission with Bearing Tools for Gato only. No CTD. Tried it again with Bearing Tools as is. No CTD. Say wut??
