View Full Version : [REL] Solution Solver 2.3
See Post #2 for videos.
https://docs.google.com/uc?id=1s8waP5LJ15U51uJlVLMSvgu50bjiIWXP
What's New?
+ Position Keeper integrated into the main intercept wheel.
+ Determining target course and speed from two bearing/range readings integrated into the main intercept wheel. Can be done in real-time mode or with a specific time interval.
+ New "Periscope Solver" tool designed with Wolfpack in mind.
+ Both sides of the german attack disc seen in many Silent Hunter mods now included. Click the center of the Dial to flip it over.
+ Various internal improvements.
Download:
http://www.subsim.com/radioroom/downloads.php?do=file&id=5118
Requirements:
A graphics card that is not a potato.
Since this is a .NET app written in C#, i used some Managed components of DirectX to render the dials for speed. Not all DirectX installers come with those components. So you may or may not need to run the full directX web installer to get them if they are missing from your system.
DirectX End-User Runtime Web Installer (https://www.microsoft.com/en-us/download/details.aspx?id=35)
Credits:
Dial Artwork:
Based off a design by 'Reaper7'
Originally designed by 'CapnScurvy'
SpeedSolver Artwork:
Based off the U-Jagd Tools for SH3 by 'joegrundman'
Attack Disc Artwork:
Hitman?
If you enjoyed the program and would like to buy me a beer (or two) for the countless hours that went into making it:
https://docs.google.com/uc?id=1kc25X_I48Cvou-Qp6ywgTkoNZLjIL1jI (https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=H6N53FRLVDKW8¤cy_code=USD&bn=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted)
Screenshots:
Lead Solver / Intercept Wheel:
https://docs.google.com/uc?id=1s8waP5LJ15U51uJlVLMSvgu50bjiIWXP
Speed Solver:
https://docs.google.com/uc?id=1-Bw-_POsah5E_jj8IMV3uSCYl2Bl7eiB
Periscope Solver:
https://docs.google.com/uc?id=1BQeAJQCk4oEiRr3ir9JJqFtCa8PRy3X-
Attack Disc Front:
https://docs.google.com/uc?id=1YQ9uZnUBVynt_wbP4kHHiM47MxfOKFRQ
Attack Disc Back:
https://docs.google.com/uc?id=1uH6bazkKxmk3KaDmasfBNJYpdkMbVz7g
Hydrophone Tracker:
https://docs.google.com/uc?id=1ZLjJAcRmjNKiTnPIyOyZUe1CWnH4cdWA
^NOTE: this screenshot was taken during development and is showing an incorrect solution due to a bug that was fixed. DONT use it as an actual example.
Overview of Intercept Wheel and demonstration:
https://www.youtube.com/watch?v=LFLbRzg7LJo&feature=youtu.be
The New Periscope Solver (designed with Wolfpack In mind):
https://www.youtube.com/watch?v=pqVb-vpCDd4&feature=youtu.be
Using the Intercept Wheel in Wolfpack
https://www.youtube.com/watch?v=voZ5qAtIl1E
Useful Resources:
For help in understanding the Hydrophone Tracker Tool:
Sonar_Tracking.pdf (https://drive.google.com/open?id=1tNWM2fxefmc3JVojc9ri0E1dgjd95_iT)
For How to use the german attack disc:
Attack_Disc_Handbook.pdf (https://drive.google.com/open?id=1zdCBmJ8b5lq8_XCRzSmC4DddoU_3dw6a)
snailer
04-05-19, 05:04 PM
Useful Resources:
For help in understanding the Hydrophone Tracker Tool:
Sonar Track.pdf (https://drive.google.com/open?id=1tNWM2fxefmc3JVojc9ri0E1dgjd95_iT)
For How to use the german attack disc:
Attack_Disc_Handbook.pdf (https://drive.google.com/open?id=1zdCBmJ8b5lq8_XCRzSmC4DddoU_3dw6a)
Thank you very much for all the work you've done.
:Kaleun_Salute:
By the way, for those who claimed that the last version was a Trojan,
here's the 2.3 Virus Total scan result (https://www.virustotal.com/gui/file/22441e143313cb083d78669b832bf707995445f9ad8e1f9a67 96923ca71ac052/detection)
Small update.
Increased the horizontal ticks on the periscope solver from 20 to 30. Ran into an issue last night in Wolfpack where i ran out of horizontal ticks :)
version is now 2.3.1.
Gutted, can you shrink the area around the (attack-)disks where you can grab it to turn? For example, I can grab the time disk within the 'small marks'-space of the adjacent distance scale. You have some kind of shadowy border there. This screws up turnradius calculations for me.
[Edit] and an optional feature, please. A free pointer across time to angle sine scale.
I know what you mean about the attack discs. The issue is the original artwork (not made by me) has a bit of a drop shadow around the dials to make them look nice. For non circular dials, the code checks for an empty pixel to determine if the mouse is on the dial, and these shadows are not empty. The purely circular dials are done through a radius check. The dial you are referring to has an appendage sticking off of it, and so is done through a pixel check.
Will see about trying to "erase" the outer shadows in photoshop.
Redownload 2.3.1. I removed the shadows around the two inner dials of the calculator side of the attack disc. Let me know how that works out for you. I erased up to the border as close as i could without making the anti-aliased edge of the dials look terrible.
I'll do the front side when i get around to adding that "free" pointer you suggested.
Nice. It's better, but not all around the circumferences up to the edge. If it is too hard to trim it further then it will have to do. I'll make a note of it in my procedure descriptions anyway.
BTW, free pointer is only desirable for the time disk side.
BTW, free pointer is only desirable for the time disk side.
Yup. Already understood. And i will double check the shadows again. It's possible i missed some spots.
Can you also add the ability to place (multiple) customized marks to the disks? (at run time) I have sometimes a need for magic numbers in calculations. Like the scratch marks I suggested way back in time for the RAOBF for speed and zoom calculation purposes. It doesn't have to by very artistic, just a short radial line enough to notice on specific disks.
Uploaded version 2.3.2.
Added an extra pointer to the back of the attack disc. Enable it through the settings.
Actually did it last night, but got sidetracked and forgot to upload it :O:
Thanks, much more flexible with that free pointer like this.
I noticed some excentric movement as the middle (distance/speed) disk is moved around. It it correctly centered? Or is this a non-circular image?
It it correctly centered? Or is this a non-circular image?
You'd have to ask the person who made that artwork. It is literally the same graphics files from the wolves of steel mod.
The lead solver disc had the same issues years ago, because the artwork was reaper7's work. I had to completely remake them from scratch in Adobe Illustrator to get them to be perfectly circular and everything lined up with no wobble. That took alot of time.
Im not doing that again for the attack disc, because frankly i dont even need or use it with all the other tools available. I added it because someone requested it. All of the hash marks line up with each other as its rotated, a slight visible wobble wont hurt.
Ok, it doesn't lead to gross errors. I know it can be a big task. I remember working on the 3-bearing AOB finder in my dreams the days after.
Awesone ! I would have liked to be able, in "AOB finder" when I save by pressing the + , the dimensions of the boat ... Alas it is necessary to reenter those dimensions each time .... Great tool anyway :Kaleun_Thumbs_Up:
Awesone ! I would have liked to be able, in "AOB finder" when I save by pressing the + , the dimensions of the boat ... Alas it is necessary to reenter those dimensions each time .... Great tool anyway :Kaleun_Thumbs_Up:
It does save them, thats the whole purpose of the feature.
Pushing the + sign adds a new contact to the list. It starts the contact off with the same dimensions that was currently displayed (ie. dimensions of the previously selected ship). Once you enter the new dimensions on any selected contact it remembers them for that contact.
Summary:
Push the + sign button to add a new contact, then enter its dimensions. It is now saved for that contact. Everytime you reselect that contact, the dimensions for that ship will be called up.
No it doesn't for me ... I run windows 7 64bits , application with admistrator rights and all security checked .... I don"t understand .. v2.3.2.0 How do you call the save boat ? Just clicking on it ? No still the last dimension entered ...
Aktungbby
05-25-19, 01:41 PM
Gali!:Kaleun_Salute: AFTER A TEN YEAR SILENT RUN!
No still the last dimension entered ...
Are you talking about ship measurements in meters, or degrees on the periscope?
Ooops yeah it works, i feel confused... what i was doing is enter new dimensions on a selected already save ship, then the datas changed .....:k_confused:
Now i'm ready for 150k !!!
:Kaleun_Cheers:
birkenmoped
06-04-19, 04:34 PM
Hello gutted! Thanks for your work and this great tool! :Kaleun_Thumbs_Up:
A dream would be a "Solution Solver" version for tablets like iPad. The handling would be very similar to a real "disc" and you wouldn't have to play in window mode or tab out to use it. :arrgh!:
Hehe, true... I went so far as to set up a virtual machine with Solver running on it, and then remote-desktop onto the VM from my tablet :)
Didn't work too well, touch/rightclick issues :(
A dream would be a "Solution Solver" version for tablets like iPad.
With a grand total of zero donations... i wouldn't hold your breath for one. Though if i ever do, it would be on android or surface because A) I dont own a mac. And B) I never will own a mac, so an IPad version is never going to happen.
birkenmoped
06-05-19, 11:44 AM
Oh, I'm sorry about zero donation. Then I guess I'll put something in the developer's coffee/beer cash box. I thought, the others (TM) have already done this generously! :oops:
:Kaleun_Cheers:
Very slight update.
Was looking into a DPI scaling issue and noticed that the new Periscope Solver control would pointlessly redraw itself whenever the mouse moved even if no mouse buttons were held down. Sounds minor, but after noticing the misplaced Render() call.. it was bugging me. The only way YOU would have ever noticed it yourself is if you somehow had task manager open and saw GPU activity when moving your mouse across the control with no buttons held down.
New version is 2.3.3
kaptnkrunch
07-30-19, 08:59 PM
ok.. so tried running this on Win 10 and in compatibility mode Win 8 .. cannot get it to run.. any ideas? Thanks!!
birkenmoped
07-31-19, 09:33 AM
No probs on Win10 on my side.
Do you checked:
Requirements:
A graphics card that is not a potato.
Since this is a .NET app written in C#, i used some Managed components of DirectX to render the dials for speed. Not all DirectX installers come with those components. So you may or may not need to run the full directX web installer to get them if they are missing from your system.
DirectX End-User Runtime Web Installer
See also first Posting
We needed to install this first on a Win10 Tablet...
kaptnkrunch
07-31-19, 09:50 AM
No probs on Win10 on my side.
Do you checked:
Requirements:
A graphics card that is not a potato.
Since this is a .NET app written in C#, i used some Managed components of DirectX to render the dials for speed. Not all DirectX installers come with those components. So you may or may not need to run the full directX web installer to get them if they are missing from your system.
DirectX End-User Runtime Web Installer
See also first Posting
We needed to install this first on a Win10 Tablet...
I saw that.. graphics is new GForce.. I will check DirectX install. The computer I have is less than 30 days old.. latest Win 10 updates..
birkenmoped
07-31-19, 10:00 AM
My gaming computer had probably already installed all important DirectX components through various game installations. So I had no problems running the Solution Solver.
On the "virgin" Win10 Tablet, the DirectX web installer was necessary, although I assumed that DirectX was delivered completely with Windows 10!
kaptnkrunch
07-31-19, 06:04 PM
My gaming computer had probably already installed all important DirectX components through various game installations. So I had no problems running the Solution Solver.
On the "virgin" Win10 Tablet, the DirectX web installer was necessary, although I assumed that DirectX was delivered completely with Windows 10!
OK.. so lesson learned .. new gaming PC does NOT mean latest and greatest DirectX
Installed / updated DirectX - fixed all my problems
Thanks!!!!
I think I've noted a slight error on the KM attack disc that's been there since it was originally made.
Looking at the speed ring on the ahistorical reverse side the location of the long mark to indicate 3.2 knots appears to be inaccurately scrunched up only 2 marks from 3.1 knots. Looking back at old copies of the printable disk shows the same discrepency, and you can see it in the images for the original Angriffsscheibe Handbuch from 2008.
I assume its an error since it doesn't seem in proportion to the rest of the log scale. Is it worth anyone's time to fix this? I dunno. :P
I think I've noted a slight error on the KM attack disc that's been there since it was originally made.
Looking at the speed ring on the ahistorical reverse side the location of the long mark to indicate 3.2 knots appears to be inaccurately scrunched up only 2 marks from 3.1 knots. Looking back at old copies of the printable disk shows the same discrepency, and you can see it in the images for the original Angriffsscheibe Handbuch from 2008.
I assume its an error since it doesn't seem in proportion to the rest of the log scale. Is it worth anyone's time to fix this? I dunno. :PI am hazarding a guess that this is an intended feature . It is in fact the 3.14 mark. And you could use this as the number pi in some calculations. It is replicated on both distance and speed scales.
That is interesting and makes sense. Two thoughts. One, I think it would make more sense to include such a feature as a specially coloured mark to make it easier to scan past it when not used (and find it when desired). Two, on the meters scale it appears that the mark is additional to the 3100 and 3200 marks while on the knots scale the 3.2 knot mark is not emphasized and is level with the other lower marks.
I think the omission of the higher 3.2 mark is unintentional since there is no omission on the meters scale.
...
I think the omission of the higher 3.2 mark is unintentional since there is no omission on the meters scale.The 3.2 nautical mile mark is slightly higher than the small digit ones on my physical printed attackdisk. I think it was drawn with a purpose.
When I look closely at the print version yes I see it, but that subtle indicator doesn't appear to be on the Solution Solver version of it.
I think the fact that it was overlooked when the wheel was redone demonstrates the less than ideal way that's been indicated.
P.Konrad
03-12-20, 08:57 AM
Great stuff mate, works like a charm. My lines where not perfect but they showed up within 100 yards from 9.4nm starting distance. I used the sonar tracking PDF.
https://drive.google.com/file/d/1tNWM2fxefmc3JVojc9ri0E1dgjd95_iT/view
Superb. Highly recommended. 10/10 Kindest regards Paul.:Kaleun_Salute:
DakotaDreamer
04-13-20, 04:51 PM
Newcomer here... I can't get the results in my 2.3.3 Hydrophone tool to match what's in the examples.
Example:
3089
Mine:
3090
What am I doing wrong here? I've looked at my entered values and clicked send in various orders. I can't see the difference.
PS How to get the inline image to show inline at full size? Looked in the bbcode info for 'attach' nothing there. Also clicking opens a new tab with the thumbnail and when yu close that you see the full size overlay over the original image??? Sorry guys, like I said I am a newcomer.
There is nothing wrong with your result. The example is somehow in error. Maybe made before a bug was fixed.
The example shows an approaching target. But like your results, it is infact a receding target. Bearing differences of 7 between B1 and B2, and total bearing difference B3-B1 of 13 indicate an AOB of 117 at B1 and 130 at B3. Bearings are contracting, meaning it is going to the horizon. Your earned your dolphins. :Kaleun_Thumbs_Up:
When I click on the thumbnails it opens as a new tab in my browser showing the thumbnail again. When I close it, the original tab shows your images in a larger, properly readable preview screen. (in Chrome)
DakotaDreamer
04-13-20, 07:40 PM
On the Hydrophone tool, thank you. I thought my result made sense. Reducing bearing change means receding target.
On the posting of images, I will move that discussion to Comments to SUBSIM Review (https://www.subsim.com/radioroom/forumdisplay.php?f=172) which is the closest area to forum help topics I can find.
DakotaDreamer
04-14-20, 05:07 PM
Newcomer here: Hydrophone plotter - I understand the mapping of the initial three bearings into the course of the target. How do I get the Range on Bearing 4? Let's say I have it set for 10 min intervals. Do I
1. Plot board - plot my own position with the predicted bearing 4
2. Move out briskly and change position for say 8 minutes
3. Stop
4. Take a new bearing and plot that to cross the predicted bearing 4, giving my range?
5. Measure the distance to the crossing along bearing 4 (not the one I just took).
Is that the meaning of "Range on Bearing 4"?
Yes, take 3 bearings from stationary position. Determine target course. Predict the 4th from stationary position. Move away from stationary position. (Often parallel course gets a nice crossing.) Take real 4th bearing from new vantage point and locate target at cross-bearing. All time intervals between bearings should be equal. So no 10,10,8. Then measure distance moved through bearings and triangulated position. Calculate speed based on interval.
(There are other 4 bearing methods that work in a different way and can be done moving all the time. See some PDFs in my lowest signature link. They have to be drawn manually on the map, Gutted's program doesn't work like that.)
DakotaDreamer
04-15-20, 12:20 PM
@Pisces thank you for the info. I played with it in Tutorial mode last night and my results are mixed. I'm taking optical observations with the periscope for the bearings to make sure my bearing errors are minimal, yet out of 4 scenarios I got one perfect target course and speed, and three for which the course was way off. I need to figure out where the problem is (me being most likely, but taking those bearings is drop dead easy and I triple check them).
I saved the numbers and will plot them on the board today. I'll also look at your tools. I really need to be able to plot the convoy course and speed while under way. I hate the thought of guessing the AOB "by eye" and having the target course solves that problem the right way (I know they can zig so maybe I'm dreaming). It (under-way plotting) can be done on the plot table, but it's work-intensive and error prone, especially while playing solo. I'm not even ready to join a crew and get us sunk or cause misses ha ha.
DakotaDreamer
04-15-20, 07:00 PM
I got the Four_bearings_method_revised_v2, Neuro.pdf. Thanks very very much. I have more to learn :-)
:Kaleun_Salute:
Be aware that these 3-4 bearing methods are time intensive. They work as long as you don't get spotted. And who knows, later in development convoys might change course when you don't expect it. Invalidating the work done. It's better to have something crude than have nothing at all. But without visual contact these bearing-methods are all you have.
Visual perception of AOB is recommended. I hated it myself in the beginning being a sucker for precision. But over the years learned to embrace it. Because it is the quickest and (with certain error) the most sure way to know what it actually is. Hazard to take a guess when looking at it, it costs nothing. And when you match it with information gathered later on you'll get beter at it. Specific angles can be quite accurate to perceive if you look at the details. (0, 90, 180) Start with a crude perception of AOB, then use that to move to a better position to ascertain those precise ones. All the while checking if all your estimations/measurements still hold up to the current state of affairs. (To stay with the Easter mindset :) ) Don't put all your eggs in one basket.
For another visual 'bearing' method you might want to consider the following thread in the SH3 section. It is based on historical logs and actual German doctrine: https://www.subsim.com/radioroom/showthread.php?t=222377
ljqcn101
04-22-20, 11:16 AM
There're other programs that can help you if you want your uboat moving all the time. Those are generally speaking TMA methods.
The Maneubo, if you're comfortable with clicking and setting numbers in a UI: http://www.adammil.net/Maneubo/
Or some TMA calculators, if you're comfortable with typing numbers in a console:
ljqcn101
04-26-20, 05:51 AM
(There are other 4 bearing methods that work in a different way and can be done moving all the time. See some PDFs in my lowest signature link. They have to be drawn manually on the map, Gutted's program doesn't work like that.)
Gutted's hydrophone tracker can still be used under a constant moving condition in some way. The theory is that, the same formula used to extrapolate the 4th bearing when stationary can also be used when ownship is moving at a constant speed & course.
https://www.subsim.com/radioroom/picture.php?albumid=1215&pictureid=10318
It can be used to predict the 4th 'imaginary' bearing. But the plot it provides falls apart if you are moving. You would need to plot your predicted position along the old course for the 4th instant and draw it on the map yourself anyway. Then find the intersection with the bearing from your actual position.
ljqcn101
04-26-20, 09:56 AM
Yes exactly. If someone wants to save time by using the hydrophone tracker to get the 4th 'imaginary' bearing then he/she could work this way.
When ownship is constantly moving, the plot this program provides can be deemed as a relative motion plot, which is also useful in a Maneuvering Board if someone wants to try out the historical 2x3 bearing method (https://www.subsim.com/radioroom/showthread.php?t=240739), but it could be more time consuming too.
Anyways just some of the many ways to do TMA.
Captain Prise
10-09-20, 12:12 AM
neat app but how does the clock work? could anyone help me? thanks
neat app but how does the clock work? could anyone help me? thanksBe stopped, or only move forward while the periscope is pointing forward or aft and you are turned facing or away from the target.
Start the clock when the target starts crossing the line with it's bow.
Stop the clock when it leaves the line with the stern.
Look at the scales which are closest to the length of the target:
The needle crosses the scale where that length of target would have that speed. On the other length scale it would have a different speed. If your target has a speed somewhere in between you need to adjust the result to best reflect it.
If it has length 125m, then take the average of the crossing points on the 100m and 150m scale.
If it has length 110m, then take the difference in speeds indicated on both scales, divide by 5 (or shift the decimal to the left and multiply by 2), then add that to the speed indicated on the lower length scale.
It's not as useful if you want precision. But it indicates a quick ballpark.
Using the calculator side of the attackdisk can be much more straight forward quickly. Align target length on the yellowish distance scale with the time in seconds on the white time disk. Pointer on the time disk points to speed in knots on the yellowish speed scale (in the middle of it).
There is nothing wrong with your result. The example is somehow in error. Maybe made before a bug was fixed.
correct, and im too lazy to update the screenshot :)
Added a note under the hydrophone screenshot to not use it as an example.
version 2.3.4 was uploaded
Small fix for the settings dialog box. It was not reading the saved value for OwnShip default speed, and was always setting the control to the default value of 3.
Rand(0)
03-25-23, 05:59 AM
Great all-in-one application, thank you for creating it.
Would it be possible to let the user enter custom zoom levels for the periscope solver?
Aktungbby
03-25-23, 05:35 PM
Rand(0)!:Kaleun_Salute:
Is there a way to snap the second pointer (attack disc backside) to a certain value (57.3 seconds) for navigation turn radius?
On my physical disk I just made a marker with my pen. I would advise against making a snap-lock point as that might disrupt any calculations when you are not needing that specific point. It could result in incorrect calculations involving time because of the snap.
Instead I would suggest to change the template to emphasize that point. Useful points are imho: 180/pi seconds (57.3 on the orange Zeit disk; or 9m33s on the minute scale) Align distance in the turn on the distance scale to the angle turn shown as seconds (not minutes!). So a full 360 degrees turn is 36(0) seconds marker or the white 6th minute marker. Then the 180/pi marker points to the radius on the distance scale. Check 6283m to 36(0) seconds and 1000m as radius at 57.3 marker.
Similarly as I suggested OneLifeCrissis back in the day for the speed calculation and zoom-factor correction magic-number on the RAOBF)
Also, there is already a Pi marker at 3140m on the distance scale, and 3.14knots on the speed scale. I haven't found a good use in calculations for those though.
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.