![]() |
Quote:
|
Quote:
To use separeted engines, first enable those patches in patcher, then you can set a hotkey via fileviewer to press before using 1/2/3 etc keys on keyboard (but not imperative - you can still use the traditional cursor) when the little right or left shaft button is selected. Beware only right shaft is working correctly (at least here) using cursor, and the RPM gauges are inversed! |
Quote:
|
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
v7.5.0 test version 12 released. Available here: http://www.mediafire.com/?52pr5d581wpwcc1 this is needed to fix bug with stadimeter button in scope views: http://www.mediafire.com/?v8cjgjh2s14337j Unzip and place in the test version's \data\Scripts\Menu folder letting it overwrite the old one changes/additions in this test version: - added a new user option that controls the starting and minimum width of the messagebox. Minimum width is 180.0. Default is 315.0 (stock size). (MessageBoxMinimumWidth) - revised Automation so that it dynamically 'loads' the commands for the script when script is played. When script is stopped the commands are 'unloaded' to free memory. This dramatically reduces the memory used with all the scripts loaded in. - when Disable sextant is clicked in the sextant window it will also disable the sextant window now - fixed bug of being able to close sextant window while sextant was active (if this happened then there was no way to deactivate sextant!) - fixed bug of button for using sextant disappearing after using the sextant I finally rewrote automation so that it's way more memory friendly :D Fixed many bugs with the sextant window staying visible and/or the button for use sextant staying visible Greetings from a small island in the south pacific :cool: |
Thanks for new test version :up:
Quote:
|
New little bug using latest NewUIs test version 12 (sorry!):
- when using attack scope stadimeter, each time i clic to match the top mast, the little icon (same as in sextant causing problem staying) at top of dial desappear! I have to double clic the TDC on/off round button to make it appear again. I'm sure you'll have a look on it :up: |
Quote:
Quote:
|
Quote:
Are you saying that the buttons are included in the latest UI version?:hmmm: If they are, then my problem is completly solved. The only reason I've delayed the latest UI is because I thought I would lose the two engine buttons on the HUD. D40 Quote:
Alright. I think I'm starting to see what's up here. I need to look for a screen shot of the latest UI so I can visualize the controls. I didn't know what the latest UI had in the way of engine controls for the mouse. If I load it up I've got an hour of set up time at least, so I wanted to make sure. Sounds like everything is there and I should just go ahead and upgrade the UI. Thanks for the response. D40:up: |
|
Quote:
Danke Fifi D40 |
Quote:
Quote:
Quote:
Did not work at first, since I did not change pixelation at first from 315.0 to 285. Since you were surprised that I was able to change the messagebox in earlier versions, I took for granted that all that was needed was a new command, messageboxminimumwidth instead of hard coding. Reasons why I was probably able to change the messagebox in earlier versions: Changing mods at bunker generally, not new campaign. Final straw and real reason- 50 CTDs, 3-4 rotating saves since at bunker. DID NOT want to start over this time. (Not the first time I've had similar issues, very random though.) using two ATI HD 4670 crossfired, now and then CTDs at depths of > 140m with lots of escorts above me. Could only play game for 8-9 minutes, including LOADING time of game. Did not need ATI driver updates. DBGview reported: DXX64: Warn: Registry value too long: MainVideo_SET in SYSTEM\ControlSet001\Control\CLASS\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000\UMD, other similar keys; further investigation: something like MainVideo_SET 0,1,2,3 (don't have accurate data anymore.) Searched many help forums. I've built enough computers, professional tech as well as personal/hobby, and know registry extremely well. Could not solve this way. Saved game differently. I had enough time to play for only 3 minutes at TC32 to play it safe without CTD. Eventually got back to bunker. Time to buy a new hardware toy. First in 3 years now. ATI HD 7870:yeah: Continuing same campaign!! I read somewhere along SH5 mods today that Fifi overclocks CPU and has seen less CTDs. That is one thing I have not done. |
Applications folder
TDW,
NewUIs with TDC, version 7.5, test version 12. Are you aware that files in the data\applications folder are much older versions than what is currently available? Generic Patcher is 1.0.94, not current version 1.0.147. OptionsFileEditorViewer version 1.0.28. I have used your OptionsFileEditorViewer version 1.0.31 and 1.0.32 successfully. Hotkey reports txt work fine in both. |
Quote:
But honestly i don't get CTDs with my stock I7 875K. Only when forcing time compression so far... and using radio patches with the burning bug... |
Quote:
Quote:
|
Perfect, thanks!
And have a nice stay on your island :up: South Pacific islands are cool, aren't they? :D (except for internet) EDIT: working fine again! Good job! |
All times are GMT -5. The time now is 10:47 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.