Fri13

Exporting the map box could be nice thing for many.

White pixels jumping around usually meant problems in either clockspeeds, a VRAM or GPU. Try to underclock card for both.

Thanks for confirming that it is on my end. The slow repair didn't offer any help. But this was a fresh new install (clear user configs and DCS).

I didn't. A pre-made weapon loadout. I just don't get my head around as everything should be properly set. Made a quick hot-ramp start-up test for a track file. Temp_1.trk If you can check that does it happen to show on you that I would be firing the cannon before and after rockets, it could solve that it is just on my side?

On me it doesn't happen that way. It stays silent. Seems that I need to fill a report with track file for it. I expected that, as it should be for the jammed weapon, but tried it few times nevertheless if it would help for some reason (why included it in those all).

While the moving map with a paper map is known thing at the era, those implementations differ. Example in that picture you can see that the position is shown with a physical pointer that can only move left/right, and is always positioned to center. And then the vertical position is changed by winding the paper map on the rolls. In a some manner you could have the map with very long strip as route, and you would not need to care much "there and back" as it could show it right. But IMHO the Mi-24 used design is better, as you swap the board in the box and the strip moves around (vertically and horizontally) and you have stationary map all the time in the box. For some reason I like more of these physical paper map boxes than digital ones. I am just little annoyed that what map is used in Mi-24, and how the waypoints gets all mushed together if you have them close by. Basically rendering them unusable for simple "there and back" as training ground map. But they are good at those long routes when you can see each leg markings nicely.

Doesn't help. That is up, but cannon can't be fired. Rockets go, but cannon stays silent. I get cannon active only after some time when Petrovich has launched couple missiles or I have put 1/2-3/4 of rockets out. Sometimes it has worked as first thing, but that has been rare. I just need to wait that Petrovich says that weapons are ready, use rockets and let him launch missiles and then check is it that time possible use a cannon. So he does something in his cockpit to enable cannon fire.

You estimate target range by visually. Just by the experience. You use the terrain elements and situational awareness to know that what is your range. First I recommend learning that by using labels. You get quickly hang of it that what is the range by at least 500 m level, and then you can start disabling the labels when you are comfortable with it. You just go by "shoot, check, correct, shoot" a lot at first. At close ranges you just need your fixed sight and you already know where you are going to hit. It can be just now very challenging because AI knows your flight path because your controller, so they can predict perfect shots. But that is as well their weakness that as long you keep small movement on the cyclic to pull variable pitch or roll based target aspect, they don't hit you (you control their accuracy, that is totally unrealistic). The other problem is that we don't have damage modeling for ground units and no fragmentation for rockets and shells. And that means you need to be far more accurate with the weapons than you should. So, you will have plenty if annoying time to learn to use area of effect weapons in manual mode, trying to hit a driver in the cockpit with the rocket or shell, while you need to give them false positions to shoot at...

I like to use the cannon in low speed for nice "sniping". It is so accurate at flat terrain that you are just "cleaning the area" with it. But, in the danger close pop-up attacks, it is high speed. That recoil makes it easy to hit targets even if you manage to already pull little over the target, the recoil pulls nose nicely down and you get likely hit. I have come to trust more of the fixed reticle than calculated one, as it requires so ridiculous altitudes (500-700 m) and high dive angles (20-30 degree) to be usable, leading often to overspeed and high risk to maneuver while AI is shooting you down. There is just something fancy with that single tapping capability. If you have a lot of trucks, APC and such, they can be so nicely destroyed without wasting rockets or anything else.

What does Petrovich need to do in the front cockpit to make 30 mm cannon possible be shot? Player can make the rockets launchable just by flipping few switches and selecting "rockets" in his weapons panel, but not the 30 mm cannon.

Placeholder. I am hoping to see a proper VR implantation where you can look at the sight area and then you see similar in there. So you can move head up and look around, and head back down and get the view.

It is for the collective only, for the altitude.

Yeah, fixed reticle needs to be pointing downward for system to calculate anything. So you can't hover and ambush anyone with a fixed cannon or rockets, or even missile. Yeah, easy to get so as trying to stare the moving sight, instead fixed one. But it still does work so odd manner. Doesn't really work as you are so inaccurate and you start to gain speed to get nose down enough for proper ranges.

But do you get CCIP sight moving to proper position, or are you required use fixed sight and estimate range? At longer ranges rockets spread, those are area of effect weapons after all. Problem is we don't have fragmentation modeling so you need direct hit. But that is not the question here, but that why the CCIP stays so low and incorrect until you get so close to targets that they get to shoot you first? Like how can you make a ambush from hover with rockets or gun when you don't get sight telling where you are hitting?

Either Manual/Automatic switch left of weapons selector knob. Or left edge on ASP-17 sight, the bottom black switch for Auto.

Good. As I tried to make the track for it in my first reply, but in all my tracks my helicopter crash 15-20 seconds after take-off. They don't take altitude but just keep going oddly to ground. Even if I take-off to totally different directions or methods, all just keep flying that time and then crash. So 100% impossible get any track files generated at this moment.

Autohover requires you to be in very good condition (hover) to start. The route seemed to work for me, not sure about speed. Something kept turning off after a second or two, don't remember which one.

All trimmers are gone through in this video (IIRC it is from the developer)

Check next to your left knee. You have all channels there. You press the buttons (Green = ON, Red = OFF) and you adjust them by trimming. AFAIK you don't need to be rotating knobs that you see there, while they do work. You have your automatic speed holder, hover mode, route mode etc.

Only reading it can get are radar altimeter, and vertical attitude from gyro. Both values are instant in the avionics, just by looking radar altimeter and attitude. Now, why does it take so long for CCIP to start raising from the bottom, even when it range scale works? It is waiting for that 500 meters or something ranges before it suddenly wakes up and decides "Let me show where you really shoot at". Before that you have it snoozing and drooppiing bottom. It isn't terrible at all. Need to remember that you likely have 2/4 helicopters in one wave, and then 3-4 waves coming in. There is a lot of firepower just with rockets. Then you fly to rearm and return to do same. Enemy can't hold their ground for long against such attacks. I really like the S-5 rockets. 128 of them and 4 ATGM. That makes very effective attack. My usual test group was scattered to 200 x 500 meters area. 4x AAVP-7 2x M-113 2x HMMV And it was surprising easy to annihilate everyone with rockets and gun. It requires 2-3 straight over flying. And typically third is the one when you get shot down. Adding 4x ATGM to beging and you get all APC really easily, then finish with gun and rockets. I haven't tested against infantry, as infantry is abysmal in DCS. That is the problem, manually requiring to aim with fixed pipper. Range is there, but at the moment it is not much better than Mi-8. With such system I would have replaced it 30n years ago for something that gives some estimation even. I believe you should have a good idea at to that 3-4 km range, not accurate but area effect. Now the rockets hit so close grouping that it is difficult to aim. And I have so far being doing this testing at the famous X field at Caucasus. So flat terrain to start. But it can't be so that one needs to dive in 30° angle to get accurate pipper...?

What is your altitude? Try to pop-up over 500 meters to engage targets at 2 km. Would need to turn labels on to see proper ranges and how really the pipper works at higher altitudes.

And why would it when it has a 30 mm accurate 250 shell cannon? Probably replace a one circuit board in box that is associated with specific weapon selector position for calculating parameters and then the selector panel with proper labels. All done in logic that doesn't cause conflict with other weapons. But just to use them as in Mi-8, you probably could just mount them and select GUV position as you say. And then use manual ranging. AFAIK the Mi-24V should be easy. Front cockpit layout to be redone from the front and left, add the rotating gunsight for operator and remove the 30 mm cannon externally, and slight modification to commander weapons panel to fire YakB in fixed position in case of emergency. I would pay extra 30€ for Mi-24V variant in 3 years from now. For SPO-15 I would leave them as is out. Only really reason why, I would like to have a proper SPO-15 for Su-25A, Su-27S and MiG-29's. But because ED is making MiG-29A, it means that they would update the SPO-15 logic and functionality to other modules. This BECAUSE they said that when they do full fidelity module with SPO-15 then they will fix FC3 planes with it.

Why? If in real one doesn't need trim reset as stick is physically right there at corresponding position. Why to deny Mi-8 style trimming where one press button 3-4 times a second in approach etc? Not activated. All assisting things off. Next time need to make video of it.