Ok so this is an update about the version 1.10 beta technology demonstrator I am going to make.
First, about the "proximity bomb".
I just couldn't get it to detonate when close to a target, nor could I detonate it at a given altitude.
So I found a different way to make a weapon that can effectively attack ships as well as land targets.
This was supposed to be a skip bomb, but given SP's physics, it ended up being a sea-skimming bomb that retains speed surprisingly well.
It came with a simple (as in, simple to use, NOT to design) aiming device that calculates the correct dropping course for you. Fly low, steady, and just drop it when all lights are on.
Its accuracy can hit ships from 10-14 km away, practically only limited by target acquisition range.
Now, speaking of target acquisition....
This is what the radar looks like now. Yeah, it escalated quickly, eh?
This is the new radar, let's start with the old one first.
I have made the sweeping radar more realistic, it now updates by sweeps, and will tell you whether the enemy is out of the radar arc or you simply don't have a target selected.
This one is modeled after FuG 240 Berlin, with accurate range and sweeping angle.
And now for that christmas tree stuff I posted above.....
That thing is modeled after the FuG 200 radar, which doesn't sweep, and has a smaller sweep but longer range. I'm still making the instruments so it is currently only cosmetic (hell, that radar array alone takes more than 120 parts!)
One of the drawbacks of that radar is that my BMW 803 could hit it when firing at extreme (> 60 deg) AOAs.
That's all for this update. I will upload the technology demonstrator once the second radar is complete.
T
@vcharng thank you very much mate!
BTW, "<" means the "less than" sign, I guess the "bigger than" sign would be ">" or something.
@marcox43 For 240 berlin:
The rotator doing the sweep: pingpong(Time, 2) - 1
The rotator to decide the angle of the radar blip:
activation group:
Input:
(Rotator range 180, speed 100%)
The piston that decides how far the blip goes from the center:
AG:
Input:
You will have the adjust for the starting, ending position and the range etc by yourself though.
btw... how did you manage to get the compass not torque-steering the aircraft? I'm having terrible torque issues with my aircraft...
@vcharng will need one for the 240 Berlin, and if possible, another for the 350 Naxos (360° 3.2Ghz refresh rate)
@marcox43 Which one? I practically have 4 radar screens now.... and each of them have at least two FT'd parts.
@vcharng ok, tho... mind sharing the FT inputs?, so I can make my radar screens...
@marcox43 both 404'd.
And don't bother, I have already finished the Lichtenstein display, please don't make me do it again.....
Awesome!
@vcharng this is the indicator screen for the FuG 200 https://www.radarworld.org/images/scans/SG2001.jpg
http://www.luftarchiv.de/bordgerate/fug2001.jpg
@marcox43 I think it means the radar "swings" +/- 55 degrees.
In my take I made it rotate 54 degrees to each side (because easier to code), and only show targets within that range.
It is hard to make a +/-55 deg arc in SP's systems, so I made the screen to have a 180 deg arc, but only the front 110 degrees (+/- 55 deg) is used.
I am going to use the Lichtenstein display for my FuG 200 radar. I will not touch the Berlin but I'll remake the FuG 200 so that it has the performance of FuG200 (except range) but uses the interface of Lichtenstein.
The page about Lichtenstein in the PPT you shared is kinda chaotic because the author copy-pasted the radar screen from other pages.... I will try my best to make a version that will both work in SP and more or less resembles the real thing.
@vcharng true... maybe it only uses the 55° region that the 240 uses. Tho, I have a question, the 55° wide scan is for the antena alone (constant 55° but sweeping) or the total range is 55° and the "radar scan" is actually smaller?
@marcox43 Not really, the 240 doesn't sweep a full 360 deg, to begin with.
@vcharng they are both Berlin models, just that the 240 is more advanced, but both use the Cavity magnetron principle. given that, they should have compatible screens.
@marcox43 Also, what you found seems to be FuG 224 Berlin A, not Fug 240 Berlin.
The one similar (in interface) to the H2S is also FuG 224.
@marcox43 ugh.... great, now I have to remake both screens....
Well this is supposed to be a tech demostrator to demonstrate the possibility of 1.10.
I think I'll make a separate, historically-accurate version when the update is officially online.
@vcharng if you have Discord, I can send ou some links that I've found over time.
@vcharng I did find the pics for the radar screen, it's a circular CRT screen. you can use the Allied H2S screen for this, since the 240 is basically a copy of it https://www.qsl.net/ab4oj/nsprog/german_radar.pdf
@marcox43 The radar screen is the last picture. It doesn't really follow the historical one because I couldn't find any reference about it.
Fug 240 Berlín... mind sharing the radar screen? I'm upgrading the cockpit of a plane that has a FuG 240 Berlín.
@AndrewGarrison please forgive my rudeness for suddenly tagging you.
I just want to know if it is allowed & possible to self-suggest one's own works to be included in the next version's introduction video? I think having a few shots from my radar system may be a good way to let people pickup what's happening with the new Target-related FT commands.
Thank you.
@vcharng Like the radar is coming!
@vcharng Yeah, you’ve gotta tag a dev or mod’s username.
@PointlessWhyshouldi oh, ok...