Not at all
Another bug: The hitbox/modules doesn’t adjust when retracting. As you see on the screenshot, the decorations (bushes), as well as the modules-view (blue) shows everything at the unretracted location and when I asked teammates to shoot the zone of the bushes, there were the impact sparks popping up.
Thats still wip dw
I mean not the same as 81C right? The actual stats are up to Gaijin. I mean up to this point CSSA5 still got HN6 which is a 12G missile.
Hello, I wanted to ask, do you think the Spyder (and other vehicles) should be able to not have the launcher up when they stop? I just thought about it and you could get you missiles shot if the launcher peeks up from a hill.
Also, does the report on the zoom include the max zoom issue? As in GSB, the camera is zoomed in to the maximum and it now has the radar covering half the screen.
The Type 81C placeholder is actually the Python 5, as shown in sensor view.
Unfortunately it’s not looking great, the missile doesn’t seem to hit anything less than 3km from you, which is insane.
The Python 5 can handle more than 50Gs but from my few plays with the stats currently given to it in the Dev it doesn’t go any further than 20G.
It is still work in progress. Once it’s renamed Python 5 and still has similar issues, I’ll just bug report it. Already got the files ready
Awesome Sauce. It’s painful seeing the capabilities of the IRIS-T and then seeing my python 5 not pulling even the slightest.
yea i notice the same thing i does not even pulling 1/4 of what it should pull pretty unrealistic the Performance of the Python-5 it should be on par with the IRIS-T
Haha, for the time being, regardless of the current ammunition data, even the missile model is IRIST, which is even more funny.
Can Spyder contain only “derby”? I mean it’s not even SR variant(I am really happy to see this vehicle in the game though thx gaijin)
It should hopefully have Python 5 and either I-Derby SR or I-Derby ER (preferably the latter).
It’s still very much WiP on dev server right now. Lots of things remain placeholder or unfinished.
Of course, there is no problem, but it is best to have both Python5 and Derby ER, otherwise the effective range will be very small. Considering that one country has obtained an SLM air Defence system with a range of 40Km, it may have to rely on Spyder MR to ensure advancedness.
We already know for sure the python 5 is coming since its flight performance are in the dev files, As for the Derby ER while there isn’t anything that can tell for sure they did mention the derby was a placeholder at the moment
Python 5 usable ingame before Python 4 is the funniest part of this whole thing lmao
Implementing 4 as an AAM is just tricky tbf. Better than what others have now, but not better than the things others would demand to counter it.
No doubt if Barak/Ra’am got it, we’d witness a 229 engine scale riot where the US players demand 9X lol.
And the Kfir C10 :D…
but regarding the performance of the P5… is it worse when launched from a static platform (Spyder) than when launched from a dynamic one (aircraft)?
Naturally yes. All missiles (and rockets in general) are.
When you’re launching from a plane, the missiles starting velocity is whatever the planes is. So if a Ra’am fires a Python at Mach 1, it’s going to have a lot more energy & range than one which starts at 0kmh off the back of a truck. Because that one is using up a lot of its fuel just catching up to the speed the air launched one started at for ‘free’.
Altitude matters too. Less air resistance up high which enables missiles to fly faster & further. Whereas down in lower denser air, there’s more air resistance, which is bad for speed & range, but good for agility as more air passes over the control surfaces.
A lot of A2A missiles that are converted for SAM usage get extra booster stages strapped to them to make up this difference (in this case - Python 5 MR / Derby MR), but those two are for Spyder MR, not AIO.