BlackPixxel

The lofting of missiles in DCS is apparently not synced in multiplayer, which causes big problems with a missile that flies for such a long time as the Aim-54 does. On the targets PC the missile will fly straight of the rail and thus through thicker air. On the F-14's PC the missile will do a loft and so it reaches the target with much higher speed and much earlier in time. This will result in the following: The target may not even get a warning of the missile when it goes active because on his PC it is slow and far away. The missile will explode far away from him (e.g. 15km in our testing) and kill him. Not sure if such a bugged weapon should be used for a competitive match.

I assume that this difference in trajectory would explain this behaviour, where the missile will just kill an aircraft that is 15km away: The target does not even get a launch warning, because on his side the missile is far away and already dead. I guess the missile made a loft, and so it had the energy to reach the target. But the target sees something else and does not even get a warning. That is a big issue in MP. I hope ED will fix this soon.

The tanks where selected in the editor, so they where full (I assume, I have no experience with the F-15). What I meant is that I can fly and keep doing crazy stuff with full afterburner until no more fuel is left. I am no longer suprised that my ER's have such a low hit ratio after seeing how this plane can be thrown around.

The speed was at M1.4 Even when pulling very slow at high speed the g indicator will go to the limit and the plane falls appart. The 7.7g peak may have been over the limit, but will it cause the plane to fall apart at the next 5.7g pull or will it just mean that the lifespan is shortened a bit? (I am aware that the F-15 is a completely different plane, I just found it interesting: With full tanks, 3 fuel tanks + AIM120's on the remaining stations I do one 11.5g pull after another with 12.5g peaks in between until the tank is empty. No damage, even though I pull over the 9g's with such a heavy load over extended periods)

It does indeed seem to be a fatigue thing. In the example I showed in the video at an earlier point 10g where pulled. But it is still very fragile: In this tacview with a fresh plane with 4xER, 2xET, 2x73 and 2xECM with 50% fuel the maximum g loading was 7.7 for a short time. Then after releasing and pulling again it snapped at just 5.7g. One other thing: In the Su-27 it is impossible to snap wings by pulling hard, because the g limiter is working everytime at any speed. In the 33, the g limiter fails to work at high speeds. The plane is pulling as if override was enabled and just breaks appart as a result. I am thinking whether the code behind the g limiter of the DCS Su-33 may just be a copy of the limiter of the 27, without taking the changed flight model into account (for example the 33 follows inputs on pitch much more aggressive than the 27 in DCS) Tacview-20190318-191649-DCS_.zip.zip

ACS was not disabled, not sure about the weight, fuel was around 5 tons and 2 ER's where already fired.

Hi, when flying fast (in the following case 1.4 mach) the wings of the Su-33 appear to become very brittle. They will just brake off at rather gentle g loadings. Here they snap at 5.2 g's: Is this intentional? It seems more like a wrong config, and it only happens hat higher speed. At low speed the plane can handle the g's at you would expect. When accelerating and reaching a certain speed, the plane starts to do a sudden pitch change and the trim is off. Maybe this is the speed at wich the wing snap mode is initiated?

The Su-33 is missing the wing flex. No movement until they just snap right of.

I use the massive jitter of the X52 slider to my advantage. I use it for the zoom of the radar/HDD in the Flanker. I always found it anoying how it would switch the zoom level when I change between the different navigation and combat modes. With the jitter of the slider, there is a constant input, so it keeps the zoom at the level I set it to, even if I switch modes.

I think they want to release it as a seperate Module, they wrote it in somewhere on Reddit. Right now it is only in FC3 for testing. Here it is:

Hello! I am aware that the MiG-29 does not feature or at least does not show datalink information on the MFD. But I am wondering if it would still be able to show the top down view of the targets of its own radar? Just like a Suchoi without AWACS still shows the targets detected by the onboard radar? With the HUD alone the situational awarenes is very limited. The pilot only sees the position of the radar contact, but not heading,speed or altitute. By changing PRF he could somewhat "filter" the targets for hot or cold, but that is all. I understand that in the concept of the MiG-29 the situational awarenes of the pilot is not really needed since he will be guided by GCI. But is there any evidence that such a top down view is really missing? Or was the decision in DCS more like "It does not have datalink so we remove the whole radar picture on MFD"? Wiki article for MiG-29C (or S) says that the radar can track up to 10 targets. What would that be required for, if not to somewhere display this information? (When it can only engage two targets at once anyway)

After take off and gear up, flaps up I always enter a weird state where the MiG just oscillates on pitch. It will pitch up, then it will deploy the leading edge flaps which causes it to pitch down, where it will undeploy the leading edge flaps and pitch up again. The 29 is a weird plane.

Yes, it cannot be that hard to implement. After all those years still nothing...

It would be great if it could carry KH25MP and KH31 in DCS as it can do according to Wikipedia. But maybe that was introduced in one of the more recent upgrades of the Su-33. No that the Hornets can carry ARMs as well

[100☭] BlackPixxel Su-33

BlackPixxel Su-33

Yes, thanks alot for helping me on Discord!

Problem is solved: Force Feedback needs to be deactivated in the game settings. Weird that it causes such an effect, but now the deadzone is gone and I can do very fine controls.

Hello Gazelle pilots! I have the following issue that makes it very unpleasant to fly this great bird: Around center stick, the heli keeps its attitute during a hover, which is fine. Now I want to roll right slightly. So I move the stick slowly to the right. But the heli will not respond. Only after a certain stick travel it will respond, but with a much higher initial roll rate than I would want to for fine controlls. I thought that this is related to the built-in deadzone of my X-52. So for troubleshooting purpose I set the Y axis saturation for pitch and roll to 9%. That means I need much larger stick deflections to achieve the desired roll rate. It also means, that I am now well outside of the built-in deadzone of the X-52 when I am giving the roll input. What I would expect is the following: For the few mm of center stick where the built-in deadzone is, the heli should not move at all. For higher stick deflections, the heli should rotate. The more the stick deflects, the faster it rotates. What I get is the following: For about 50% stick travel the heli does nothing. When I very slowly increase the stick deflection even more, the heli will appruptly begin to roll with quite a high roll roll rate. This behaviour makes it really hard to fly this bird. A heli needs very fine controll inputs and very little corrections. But with this Gazelle I cannot do little corrections. Small stick deflections will act like a deadzone with the heli not responding. Then after a millimeter more stick travel, the heli will start to roll with an initial roll rate way to high for small corrections. When I try the same thing with the reduced Y saturation on the MiG-29 it does not have this problem, which means that it should not be stick related. Does anyone have similar issues, or a solution for this problem? Thank you in advance!

Yes, the vertical EOS cursor should also be applied to the Su-27. I wonder what the reason is, at least with the MiG-29 I assume it is because slight pitch movements of the MiG make the targets go up and down quite alot on the EOS. A bigger vertical marker would make it easier to get the target locked. Or maybe the sensor has a low vertical resolution.

But then it is still buggy. When the EOS is left or right, you will see the center position targets, but you cannot lock onto them. Does anyone know how wide the area is that the EOS scans? It is the 60deg from the Su-27, or is it maybe full 120°?

Hi! There seems to be a bug with the EOS scanzone. There are keybindings to move the EOS to left, center and right. They seem to work, and the bottom horizontal line in the HUD changes just like it does with the radar scanzones. Problem is: The HUD will always show tagets as if the EOS was centered. When the EOS is left or right, a plane flying in front of you will still appear in the center of the HUD, but you cannot lock it with the cursor. I am sure that this is not supposed to happen. Does anyone have this issue too?