All Activity

ED correctly modeled the SPO. The Russian combat manuals state that the SPO cannot be used with the radar on. This isn't the lack of maintenance, but a feature of this device.

Good morning to everyone. I have a problem with Radio Transmission, no response when I try to talk with ATC (Single player). Thanks for your time

Yeah Dashomat may have a completely different problem as well, e.g. same problem as you but different problem than the original poster of this thread. They were asked for logs and not supplied them so we don't know if the problem is the same as yours. The part of your error re: "Could not resolve hostname" could entirely be due to the fact that you've turned your network off. Don't know why you're doing that though. Sounds like an easy solution then Have you tried turning on the offline mode of the game?

That’s what the rhombus (diamond) is for. To show you the direction and magnitude of antenna movement. It will cover target when in the middle

A bit of background. The Wall fell in 1989. East Germany got their Mig-29s around the same time as Yugoslavia in 1987. The Yugoslav training groups of pilots and technicians started their training after the Germans finished training. The 204th regiment was mostly based in Pleso, Zagreb, where the main repair facility for the 29s was and Batajnica, Belgrade (repair facility Moma Stanojlovic at that time did not service 29s). With civil war, the main repair facility remained in Croatia. Given the chaotic nature of withdrawal from Croatia, we can not be sure that all tools and spare parts were pulled out. This also meant that significant number of trained persona who lived and worked in Zagreb were also divided (some of them moved to Belgrade, but later left and returned to Croatia). The Federal Republic of Yugoslavia got both sanctioned and embargoed, which prevented any import of spare parts or modernization, until 1995 when the Dayton accord the things got more relaxed. The planned overhaul was supposed to start already in 1996 and be completed in 1997. Offer was received for the overhaul and upgrade (radar upgrade, R-77, Kh-29T, fixing gun/fuel tank issue, as well as possible Gardenia installation). Only radar upgrade would have brought MTBF from 50 hours to 250. By 1998 large parts of fleet were grounded, mostly due to the failing electronics. The engines were still in good condition, but on the paper the lifetime got extended at least on 2 occasion past the time the overhaul time. At this time the it was clear that Yugoslavia will be invaded by NATO, so desperate attempts were made to repair the fleet. Offer was received from MiG to service the boards, which were prone by failures of electrolytic capacitors. MiG has offered to service this in field, at the price of $200k per aircraft. The request was made in the 204th regiment and sent along the hierarchy, but the whole thing stalled: someone along the path with political background decided this is not needed. It should be noted that during the period 1996-1998, 2 complete Hinds were smuggled in the country for the needs of Serbian Police. Still this was rather sensitive internal political time. With Serbia and Montenegro leadership not getting along and later controlling the Minister of Defense, I can easily see why these opportunities to bring the Migs into fully operational state were missed. Internally leader of Serbia never trusted military (e.g. prior to the war Chief of Staff Momčilo Perišić along 20+ generals got retired and replaced), so all available money got funneled into Ministry of Interior. These "repairs" which took place at the end, were not done with official MiG support, and amounted to cannibalization of spare parts from different air-frames and and improrvized repairs. The airplanes got into somewhat flyable state with breaks occurring frequently. You will observe that this roughly correlates with the date of the intelligence document marmor posted. I am pretty sure Germans would have experienced same kind of the issues. I have no information of they themselves did overhaul. However its worth noticing that they sold their Migs to Poland basically against a symbolic price in 2004, basically at the price of junk. Perhaps some Polish MiG lovers can tell us when the overhaul took place? In 1999 war started and pilots flew in airplanes that often had failed electronics on the startup. One such case was the flight of Peric/Radosavljevic (I will prepare the story about them) and actually it might be the case of this radar/SPO bleed example. Peric was more experienced and was supposed to lead. On takeoff when turning on the radar he had immediate failure, and noticed that his SPO is lit like a Christmas tree (randomly blinking and beeping). He passed the lead to Radosavljevic, whose airplane appeared to work properly. I will not go deeper than this at this time. As for this issue in documentation: in Yugoslav manual there is no mentioning on this radar/SPO bleed issue. The document was originally published in 1990 (I assume that for 3 years they used either soviet manuals directly or had another kinds of documents to support the training and operation). The document had revisions in 1992, 1993 (large number of documents got updated at this time) with the final version in 1994. This 1994 version is what got leaked in the internet. It should be noted that was already 7th year of the service, so one would expect that they knew the airplane pretty well by this time, and that such limitation would have been documented.

I mean I have a 9.12-9.13 manual that doesn’t even mention it. We have a maintenance manual talking about how to fix it. Su-27SK manual uses the word “it’s possible.” We have pilots that said it never happened to them. Whats the most likely? Maybe it’s functional in some aircraft and not in others……

Thank you 1. I don’t know for sure, but I would bet it uses the same range/fuel consumption table I showed in my video assuming you are at that speed. That chart is everywhere you “minimum fuel consumption of MiG-29” mentioned. 2. By fuel reserve, I bet they likely mean the 550 kg when number 2 tank is just left and it shows up on Ekran 3. The hydraulics will remain powered as long as the engines spin high enough, I believe 35% rpm. Below that there will be a slight amount of time where the hydraulic pressure will be decreasing but still functional.

This log file is just from starting up the launcher, and not the game. Will need a log file from when the actual crash occurs, the log file gets overwritten every time you start the game so get the log before restarting DCS. You can also check in that Logs folder to see if you have recent ones with a name like dcs-log-<timestamp>.zip as this will contain a log and extra information when crashes occur. If so then attach one of those as well.

Am I the only one, that is a little disappointed about the amount of "yellow cross" switches in a FF module? aka unclickable switches. I know that in almost every module there are 'some' dead switches, but I prefer it if they are clicky anyway. Maybe there is stuff that will be added later, but right now I find it a bit odd.......

The monocle only works while using NVGs now... Keep the reticle as on target as possible... In my case, it sometimes work to shoot hellfires aiming just a little low. APKWS lofting is another story...

Not much, really. I'm busy setting up the Corsair and Tomcat missions with what we have now.

In TelemFFB you don't need to do anything* (apart from enabling or disabling effects an set their individual gain). In The VP config software, make sure that the dot in the monitor moves the same way as your physical stick. (Forward -> Up, Backward -> down, left - right). If you mounted the Rhino sideways or frontside back, just check the box for invert axis in the lower screen. If you set it up this way, the effects will be applied in thr right direction. Don't invert x/y axis in the sim. *actually that is not correct. For some effects, like Gun recoil, you can actually set a direction in a 360 degree range (including random). So you could set the recoil to push or to pull on your stick. That is important for pedals e.g., since they don't have a Y axis, and effects wouldn't be felt unless you change the direction by 90 degree.

After clearing out all enemies at the target airbase, I circle at low altitude while Zeus approaches. No tracers or manpads observed. Just continuous flares at southwest side. ZEUS41, taking ground fire I show of force the airbase ready to drop a cluster on someone... nothing. Zeus lands. Zeus41 - we're getting hammered here! Still nothing to be seen around the airbase... ADVISE - GREEN SMOKE = FRIENDLIES Okay, that I see, but still no enemies... MISSION FAIL - REPEAT MISSION FAIL and them immediately after mission fail, a bunch of ground units spawn around the airbase. Not sure if I'm missing something, but upon closer inspection in TacView, it appears that two of the CH47s (Zeus 41 2 and 3) are colliding after they take off and are about 100' AGL. DCS 2.9.20.15010, no mods.

What does it weigh? I live in the UK so would need to ship it.

I'm not sure B-21 have "CAS" attribute, it is a pure Bomber !

It's the resolution, You can "tweak" all day... you won't pass that limitation unless you push it. To have a base line on quality drop for a little bit the attempts on "Performance" and go balls to the wall to quality. Use for testing at least Pico Connect (free from pico). It's not better than Virtual Desktop but is allowing you to test and see a bigger resolution. Word of "caution" Pico Connect can only work with Steam VR! So you need to be careful you know how to tweak that out of the way so it doesn't create problems. Don use any super or down sampling in SteamVR. Make sure is set "manually" or "custom" to 100% resolution both in general and video. Usually is the one that reports the actual resolution when you are in game and press the hamburger button on left controller... Disable any super-sampling, menu smoothing etc all performance eaters in SteamVR. Home... Theater... OFF. If you need help later I can post some pics with Steam VR settings also. Put Pico Connect to Ultra+ which brings 3480x3480 per eye resolution - super-sampling Although the headset can only display 2160x2160 the biggest super-sampling is the better the image. There is e noticeable difference between VD on Godlike (3120x3120) and PicoConnect on Ultra+ (3480x3480)! Of course the FPS will take a hit.... You test for baseline Quality here! I stick with it but you can drop it after testing but you need to know from where you go down and how much you are OK to lose. Drop 72Hz... imho this a big placebo. It just adds flickering doesn't really increase performance. If you have 1FPS performance the fact that the system transmits and receives 90 or 72 copies of that frame makes little to no difference but the flicker hits your eyes. Go to 90Hz. Have a good Wifi 5GHz is a must or a good UTP-USB-C cable if you can't sustain good Wifi. The cable variant is not better in quality if wifi is already good it just a bit lower latency and stable as a rock. But also the wire is awful... Just for reference! A 5GHz network has a top speed around 1200Mbs - base network speed Virtual Desktop and Pico Connect can work on this network at 150Mbs on H265 (HVEC) codec. This is like the base codec speed... not actually used speed!!!!!!!! During gameplay this speed varies... usually drops! VD doesn't show it but Pico Connect shows it live and you can have between 30Mbs and 60Mbs on Ultra+ in game in 3D! (not desktop pay attention... desktop view is far lower in Pico Connect and you will see it a bit like an oil paint but it irrelevant) So think about it... the image looks extraordinary good at 3480x3480 per eye at ~40Mbs!!! Not 60Gbs like the display port can sustain... 40Mbs Mega bits per second versus 60 Gigabits per second ! I have a Pico 4 also and these are my settings. I don't go for performance. But anyone should test both ends... Performance and Quality and chose where in between he or she accepts to sit. I have 30fps in single player with Pico Connect on Ultra+... good for sight seing and Quality baseline establishment. After you did this test... then you know and you can chose your poison. null

Thanks for that/.I have this damage recorded as being caused by the following double Typhoon, Connie/Viper. Similar damage was caused to the USS Bennington and Escort Carrier, USS Windham Bay. USS Heavy Cruiser Pittsburgh lost her bow. USS Bennington. Heads rolled after the enquiry. ..

In the position of the control stick fully to the right and fully down, the cable is clipping through the metal panel.

Got it! That's a very important point! Thank you, I will not do these things again! This won't happen in every mission. Only in Mission 2. Maybe once in Mission 5, but no more. Thank you for your feedback!

Roger that. Thank you for clearing this out!

It was meant to make you aware that the wheel is behind you and to take that into account when turning so you don't turn too late or too early

Strange, I've spoken to many people, interacted on all of our social platforms. If you feel you can not give feedback in public PM me directly. Thanks

That I know of. But I am not sure what tutorial meant with this. I thought it was some "lever" inside cockpit. "Keep in mind that the strut is placed behind pilot seat". On second thought was it to raise awareness of caution during taxi ?

I've got the canopy reflections on 0 and still get way too much reflection on the visor in VR. Is there another reflections option somewhere?

It's the "thing" your nose wheel is attached to.