![]() |
|
Quote:
|
|
Thanks Nisgeis for making a version compatible with Trigger Maru I will have to try this out later tonight.:up:
Steve |
Great work! But is there any way to get it to display the ten-thousand meter's place? That would definitely help targetting calculations. Radar picks up a target at around 30 km, and until it gets within 10 km, I'm forced to guess the range. It seems to be a whole lot of extra and unnecessary work.
My idea: Retain the original 4 digits, but have them cover: [Ten Thousands] [Thousands] [Hundreds] [Tens] Instead of the current: [Thousands] [Hundreds] [Tens] [Ones] Being off by a couple of meters isn't a big deal, being off by a whole mile is. Idea 2: Keep the current: [Thousands] [Hundreds] [Tens] [Ones] But instead of having the [Thousands] dial stop at 9000 m, have it roll over. That is, 12530m would be [2][5][3][0], the same as 2530 m, but it's pretty easy to tell which range it actually is. |
Quote:
|
Quote:
e.g. Right now, 2340m is displayed as [2][3][4][0], and 22340m is displayed as [9][3][4][0]. Basically the hundred and ten-meter digits keep rolling even after 9999m, while the thousand-meter digit stops at 9. Could we have the thousand-meter digit behave similarly? That is after it goes to [9], have it roll back to [0] for 10,000 meters, [1] for 11,000 meters, etc? so basically: Actual range: 32,320 meters. Current display: [9][3][2][0] My idea: [2][3][2][0]. It's easy to tell it's around 30,000 meters from the A-scope or PPI, and now we know it's at 32320m, instead of guessing: is it 30320? 31320? 32320? 33320? 34320? 35320? With my new system, the possible ranges are 2320m, 12320m, 22320m, 32320m, etc. It's easy to tell which one you're at because there's 10,000m difference in ranges. |
I understand what you are asking for, but the game engine does not allow for rolling over of the thousands. It stops at 9. There's nothing I know of that can change it.
|
Totally awesome Nisgeis! Any news on the RFB 1.5.2 version? I cant wait!
Pretty please... :up: . |
Quote:
Waiting for this as well!:yep: |
I suppose you'd have to ask in the RFB thread. I think they were considering it for inclusion, but it was released after their freeze on new features so missed 'the boat' :D .
|
Fantastic mod.:rock:
No more comments needed;) Cheers /OB |
Quote:
|
LukeFF do you have any idea when that addition will be?
|
Quote:
|
Thanks for the fast answer LukeFF. I'll start to make a local implementation (RFB 1.52 + Patch2). If i succeed i will forward that to your team and you can use it at your descretion as long as Nisgeis gives his permit ofcourse.
|
TM1.7 question
Hi.
I have been using this nifty little mod for a while now.:yeah: I have just installed the new TM1.7 which includes among thing a three step zoom function on the scopes + a two step zoom on "UZO" and binoculars. Now, if I add the radar mod after TM1.7, the zoom functions reverts to the original version with only two steps for scopes and none at the UZO.:hmmm: Tried another thing by adding the Radar mod before TM1.7 and it works fine BUT the digital presentation of the range is no longer there...:-? Any ideas? Cheers /OB :salute: |
RESOLVED!!!!!:D
Found the correct order of install: 1) Trigger maru 1.7 2) Nsgeis Radar range mod 2.05 for TMO1.52 (mods the PPI and A-scope) 3) Max optics for TM1.7 (brings back 3 zoom levels of TM1.7) 4) Nsgeis Radar Ring and Bearing Line mod. Works like a charm again but with TM1.7 as a base. No changes needed!!!!!!:DL:DL:DL Cheers /OB :salute: |
Hmmm, that will pretty much undo anything added to the interiors of the subs with TMO 1.7. I don't know what that might be, but just be aware that you may be missing something clicky or flashy in the interiors.
|
So far I have not seen anything yet.
Fans are rotating...gauges ok...etc etc....Looks fine to me.:03: |
All times are GMT -5. The time now is 02:52 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.