![]() |
He should also try the 3GB switch since he's running XP 32bit :yep:
|
Quote:
|
Quote:
A point to note is this part :- Even with the switch Quote:
|
I saw the CTD come for me, after the system slowed down, and this state exist until a time. Firstly, I not understand why.
I found, the virus guard systems has a big priority of task, and they randomly allocated system-resources, and hold back my system performance. Thus, before I start the game, I temporary disabled the virus guard software. I not recommend this method without conditionally, because possible forget to turn on, but this was effective for me. |
Quote:
This could be a memory problem as well, please see my post 8250 above. :salute: |
Thanks Silent Steel! :salute:
I shy, download+burn+run Memtest-86, but not found any memory error. The tips of virtual memory has interesting for me. I used always the default setting of Windows7 x64. Best Regards! :up: Quote:
|
Hi everyone.
I'm running TDW's UI mod, IRAI and FX Update. When I tested compatibility with the TDC Torp Test mission, I'm getting wildly conflicting ranges between the stadimeter and my map tools (left contacts on so I can test stad accuracy). Didn't the UI mod fix the stadimeter issue? Is there something basic I'm forgetting to do? For example, when I ID a ship and take a stadi reading it should 12k+ meters. When I measure the distance on my map it is only like 3k meters. WHy the huge discrepancy? EDIT: Forgot to mention I am using 1440x900 res so installed the 8x5 manos scope mod. Is that not the correct scope patch for my resolution? |
Thank you, Silent Steel! I tried some of your suggestions but unfortunately without success. Thank you TDW for all of your contributions!
Finally I will change my system to Win7 in the near future. Of course, I will keep you informed if I was successful with installing SH5 and your mod. Until then, keep up the good work! THANK YOU! |
Quote:
Go a bit closer - say 3 to 5km max and test again:up: |
Quote:
If by IDing the ship you mean you visually spot it and see that it's an enemy vessel and you do nothing more then yes the stadimeter will be totally whacked. How you use the stadimeter also affects its accuracy. Where are you putting the first line? Where are you putting the prism split line? If you're not putting the first line directly on the waterline of the unit and/or not putting the second line at exactly the highest point on the unit then the stadimeter reading will be inaccurate. The farther the unit is away from you the harder to get an accurate stadimeter reading (due to the margin of error increase). I would have an extremely hard time getting an accurate stadimeter reading on a unit at 12k+ distance. It's almost impossible to place the 2 lines correctly at that distance. |
Quote:
That's just it. The ship I am targeting has been appropriately identified (via WEPS) and is at a range of approximately 3000 meters but the stadimeter is saying its 12,000. Something is out of whack but i can't figure out what. |
Quote:
Hi again, Please tell me which of my suggestions you tested without success and where you put it in your list. :salute: |
Quote:
|
Is there a list of keyboard commands for this mod?
The reason I ask is I believe there's an option to lock the periscope view to the target on it, as was in previous versions. I've tried pressing random keys until I'm a drooling mess, but I'm stumped. Is it something that has to be enabled somewhere in one of the python files? I did a google search and that doesn't help, tho I haven't ploughed through all 501 pages of this thread. I'm just using the stock NewUIs_TDC_6_8_0_TheDarkWraith and patch 1 and SH5 Enhanced as the UI option. Other than that, this looks to be an awesome mod :cool: |
Quote:
|
All times are GMT -5. The time now is 03:33 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 1995- 2025 Subsim®
"Subsim" is a registered trademark, all rights reserved.