xxJohnxx

Yeah. Additionally to that, you as a pilot would probably would know if your gunsight could get the radar range or just operate at a fixed distance. It is quit crucial for employing your gun... But as it has been said, Leatherneck is looking into it. If they deem that the ASP should use radar range they will change it, if not, they won't. Being rude won't help in any chase. The only thing it does is driving the devs away from the forum and worsening communications between them and the community. So if we all keep easy and don't get to emotional we will end up with a better situation for everyone! :thumbup:

It is not only been discussed now, but has been discussed several times. The devs even mentioned some upcoming changes in the last change log, so you might actually want to wait for the changes to be implemented into the sim with the next update.

Actually alot of the documentation as well as a lot articles about the aircraft mention that even the early concept and aerodynamics test aircraft could use the radar for air to air gunfight range calculation.

Maybe you can share a track? As long as landing within parameters (speed, sinkrate and especially weight) that normally doesn't happen to me.

Hi, This has been discussed here on the forums a couple of times. However, most discussion ended in nothingness, because nobody could actually provide sufficient documentation for the stuff it is supposed to do. Would be nice if you can give us some sources for the improvements you suggest, technical manuals, descriptions and the like, sure would be helpful to not just us, but also the devs! :thumbup:

Hehe, yes, that got me a couple of times in the beginning also. :pilotfly::joystick:

That is nicely done! Thanks for the work!

That is interesting indeed. In the end it probably doesn't matter to much for the simulator, but good to know! Okay, thanks for the info! Didn't really know that, but I will add it to the video! :) Yeah, I wanted to do the radar-guided missiles and chaff together with the jammer, that isn't working currently. I also hoped to do some tests then, to check if chaff and jamming would help at all against radar guided missiles. Just for a bit of intermediate information, I summed up my knowledge about radar missile avoidance in the comments to the video. Not sure if everything applies 100% to DCS, but at least that's what I know. If you have any more suggestions, please let me know! :thumbup:

Jorge, That what you are posting is correct, but I guess it is also worth to provide this additionally to what you provided: This is from page 153 of that pdf and is used for actual combat intercepts instead of max speed or max altitude flights. However, it again proofs the point of climbing at TAS. Strange to me, but it probably provides the best distance/time results for intercept.

Yes, I read that. Just in the track Alfredson provided in post #15 it took him 2 minutes and 15 seconds to climb from take-off to 10.000m. That is with full burner.

Just another thing though: You know that in the track you provided, it took you roughly 2 minutes and 15 seconds to climb from 0 to 10.000 meters? That is quit respectable climb performance if you ask me... That is interesting... Thanks for the link. Keeping the constant TAS of around 870km/h even seems to work out, altough AoA is quit high before levelling out. EDIT: I was normally using the in the included manual suggested procedure of climbing at 600km/h, that's why it seemed so odd. Keeping a constant TAS at least prevents you from going super-sonic, while you end up climbing in a high AoA flight attitude. Not sure why that is preferable, but if the real manual says so...

Hmm, okay. Well, there is some reduction in thrust with increased altitude, maybe not as dramatic as you describe it though. Can you try to hold a fixed IAS of 800-900km/h though? Because at least too me, it looks like it is decaying quit rapidly. Also worth mentioning, if you are about too pass Mach 1 it might be worth too either level out briefly or put it into afterburner for a couple of seconds, as the sound barrier adds some additional drag to the aircraft, which you might not be able to overcome if in too steep of a climb.

Hi, I had a quick look at your track file and it is quit easy what is going on. The problem is that you keep a constant TAS, which is why you run out off airspeed. I am not sure why you have been told to hold a constant TAS but, that's not the thing you want to do. But I can see the problem is down a bit deeper in the understanding of IAS (Indicated Air Speed) and TAS (True Air Speed), so let me explain. The air speed indicator shows IAS. The combined true airspeed and Mach indicator shows TAS and Mach. At sea level IAS and TAS is the same thing. 100km/h IAS are the same as 100km/h TAS. However, if you start to climb, the air will get less dense. The way how the air speed indicator works this denser air will result in a wrong (too small) value being shown. This means at a higher altitude 100km/h IAS will give you 140km/h TAS. If you climb further it increases further. As said, this is an effect off the air being less dense. However, the less dense air not only has an effect on your speed indicator but also on your aircraft itself. This means at a constant IAS the aircraft always produces the same amount of lift. This is not depended on altitude. In the MiG-21 you will be stalling at speeds lower 300km/h IAS, not depended if you are at 0m or 10000m. This now means, if you keep a TAS of 870km/h throughout the climb you may initially have an IAS of 870km/h (at sea level) but the higher you get, the slower your aircraft will become, as the IAS reduces. At 10.000m 870km/h TAS are only about 534km/h IAS, leading to the high AoA situation you are experiencing. At 15.000m 870km/h TAS are only about 371km/h IAS, close to a stall. Just to sum this up: There is no reason to look at your TAS indicator for doing anything performance related. The only reason it is there, to figure out you are actually moving through the surrounding air, and by subtracting the wind speed, how fast you move over the ground. Aircraft performance and limits are mainly depended on the indicated airspeed. The only expection to that is when you are flying fast, then the Mach indicator comes into play. EDIT: BTW: After take-off and retracting the gear put your gear lever into the "neutral" position to prevent loss of pneumatic air, else you might not have enough air left to fire the braking chute or use the wheel brakes on landing. EDIT2: Try to climb at around 900km/h IAS. That should give you a reasonable climb rate up to cruise level.

Nope, that doesn't work. The Set Internal Cargo command is not usable in multiplayer. When triggered, nothing happens.

When I overclocked my i7-3770K I just increased the default voltage around 0.1V and started to put some load on the CPU with Prim95 or Intel Burn Test. If it ran stable for some time, I would decrease the voltage by 0.02V and try again. Once I started to get BSODs, I would increase the voltage slightly again, until I found myself a good, stable value. Once I found my value, I ran a long term test (10 hours or longer) on that voltage, just to make sure everything was running as it should and within good temperature ranges.

I am not entirely sure if it fits here, but I will leave this hear anyway: {combos={{key="M"}},down = iCommandToggleMirrors, name = _('Toggle mirrors'), category = _('General')},This can be put into the MiG-21\keyboard\default.lua and can be used to toggle the mirrors on and off like in the other modules. Best regards, John

Maybe. Did you use the radio menu to select the cargo first? You have to do that before you can hook it up.

Uhh, that is a good point actually. I will have to look this up, but I guess you are right, the SOD-57 is actually just related to the ATC transponder. It looks like the SRO-2 is the IFF transponder. I actually tried to get the light blinking again, and even with different radar setups (aircraft, SAM search radars, early warning radars) I didn't manage it to blink though I remember it blinking some time ago. I am not sure what the reason for that is. Does anyone know an example where the lights start to blink during the current version of DCS? Not sure about the transponder channel selector, but I assume it doesn't do much in the simulator.

No worries! Just FYI, the mistake you made was to put the whole link into the Youtube brackets like that: [ YOUTUBE ]https://www.youtube.com/watch?v=wLIVi9sPohs[ /YOUTUBE ] (Without the blank spaces)However, the forum software does only correctly show Youtube videos when you put the part behind the v= into the Youtube brackets, like: [ YOUTUBE ]wLIVi9sPohs[ /YOUTUBE ] (Without the blank spaces):smilewink:

The Mi-8 is indeed a great bird. Hoping though they will sooner or later completely finish it though. BTW: Fixed OP's not working Youtube link:

I personally would advise against the use of overclocking software. They often imply automatic overclocking functions that set a much higher than necessary processor voltage, causing it to run much hotter than it would have too. IMHO nothing beats overclocking in the BIOS with the voltages set as low as possible, while the system still runs stable.

Hi, It has been a while, but today I got another video for you: It covers how to use the RWR and the Flare dispensers. While this might not be new to you, I also try to show some tactics on how to make the RWR just a tad more effective. Hope you can enjoy it! John

Hi, Could you please provide a track? A track can be saved on the debriefing screen after you finished a mission. You can directly upload it when creating an answer to the this thread. It would help out to figure out what the problem is. Best regards, John

Yeah, the AX1200(i) is quit impressive. The silent running on low loads (I think it was even up to around 50%) is awesome, especially on silent running rigs. It's just a pity that the Corsair Link software can be incompatible with certain motherboard chipset drivers (mainly the Intel ones) and cause Bluescreens.

Once you get used to it, it actually is quit easy to just hover above the cargo without the F2 view or the cargo cam.