What can you say !!

Updates are thick n fast, always better than the last :yeah:

:salute: Cheers

Def

Hiya's,

When at a periscope (think it maybe either one)

If i goto WO to alter the set of firing commands via the icons, it seems if i try to alter the deckgun firing routine, then goto alter the flaskgun firing routine i get an overlay of both icon strip commands (hope that makes sense)

Litterally put 3.01 in with no .py alterations if that helps

Was a saved session though so maybe it's this ??

Cheers

Def

edit: will try out of port later, gotta get gone now :( lol

Eeee... what does it mean?
:doh:

saved session doesn't matter. I'll give it a look and see what I did to possibly introduce a bug into this :up:

yep, it is broken !

... it simply wont remove handling icons of AA or deck gun if aa or deck gun handling is selected and one of this menue groups was selected before :doh:

they are overblending each other then, the before selected menu group is still showing, instead of blended out.

found the reason why this is happening and it's my error. I set an override so I can check everything that needs to be updated every cycle. This override prevents the order bars and order categories from being reset. Well I forgot to clear the override when I was done checking everything. This results in overlapping order bars. I've fixed the problem and will be issuing a bug fix for it soon.
I also discovered another bug. At game start I'm automatically asking for battery recharge when the batteries are already fully charged. I've fixed this bug also. The fix will be included in the bug fix I'll be releasing soon.

Woohoo nice work :yeah:

Def

for those of you using v3.0.1 here is a bugfix for the overlapping orders bars and automatic recharge of batteries whether they're recharged or not bugs:

http://www.filefront.com/16761461/Ne...-1-bugfix1.7z/

Unzip straight to MODS folder and enable after v3.0.1 of UIs mod. Say yes to all JSGME errors.

If you would rather use a complete new version then v3.0.2 has been released and you can find it at post #1 of this thread.

Thanks man ! :)

I dunno, i leave my boat in the safe hands of the xo to grab some fresh java, and dangnabit a fresh update :)

Ya know, one day i might finish this mission i'm on lol

Cheers Again

Def

So far it looks pretty positive that I have a solution for the speed and AOB being reset when you use the stadimeter. Still testing but preliminary results look very positive :D

Reaper7 unknowlingly provided me the missing link I've been searching for for maintaining speed and AOB when using the stadimeter with his work on trying to implement another way to do the stadimeter :rock:
You'll notice in the screenshots below that the speed and AOB dials have a red button attached to them. This red button 'sets' the speed or AOB in the TDC so that when you use the stadimeter it doesn't reset them to zero :D. The whole thing is funky in how it works - Ubi really screwed everything up here.
So let's say you have a target locked. You determine it's AOB and set the AOB dial to what you calculated. Now you have to also press the AOB's red button to 'set' it into the TDC. Now you determine the target's speed and input that into the speed dial. Now you have to press the speed dial's red button to 'set' it into the TDC. Now you want to take a range reading. You click on stadimeter and determine the target's range. Now here's where things get funky - the values you 'set' are not reset to 0 - they persist BUT the AOB target value has been reset (Ubi bug :nope:). What this means is if you mouse into the AOB dial then you will have to 'reset' the AOB to the correct value and press it's red button again to 'set' it (this is if manual input mode is enabled - if it's not enabled then mousing into the AOB dial will do nothing). Anytime you take a range reading it resets the AOB target value (this is a different value from the AOB dial's value).
Now I know someone is going to ask "Why can't it be automated?" Well the answer to that lies in the fact that I can't raise the button's click events (have tried) and I can't make the OnClick event handler fire for them either. If I could get one of them to work then there would be no need for the red buttons. Also, if I could find a way to set the TGT dials values then there would be no need for the red buttons. Once a way is found how to set dial's values (CrtVal, NewVal, etc.) it will open up a whole other level of modding SH5.
I'll write more about it and how it works tomorrow. I'm tired and wasn't going to bed until I figured this out :D
http://www.subsim.com/radioroom/pict...pictureid=2253

http://www.subsim.com/radioroom/pict...pictureid=2252

This is great news.:woot: I do have a couple requests along this topic. Could you put a Stadimeter button and Set Range button on the Range Dial to save time opening/closing XO dialog to access it.:sunny:
IMO, that entire XO dialog to Identify a Target and set a firing solution is total BS.:damn: The XO Icon should be with the rest of the Officer Icons, not drifting around getting in the way.:damn: The only thing it is good for is if used for a example of how to get Crew Commands by Dialog into the Officers Icon Menu Bar.

I was going to put the stadimeter button from the SH4 style dial thingy onto the range dial like I did with the red buttons just haven't done it yet. I'll do it now. What is the set range button that you speak of?

another request...

would it be possible to disable all this popping mouse cursors, like white and yellow hands, arrows and ****... i like moving and turning in 3d space, i often disable the UI compledly for this, but all this cursors are still popping in by turning and moving, i get stalked by the
ice-cold litte hand:timeout: