All Activity

Hi all. I have the the dcs "system" in imperial units due to I usually fly nato planes. The cockpit have imperial units. is it not possible to change it to the metric system?. Im using the cockpit in english but I want the original unit of the mig. Im looking for in special options, the manual... but I dont find nothing.

Yeah so the SPO-15 maintenance document has a whole section on "blanking" the SPO for use with the radar, so I think "as modeled" currently its some reversion mode (which well, probably right if it wasn't maintained). And post collapse of the SU I bet many countries had shortages of parts/trained techs to maintain em, so you get all the stories of it working this way. But at least based on the doc it does interface with the radar and should be usable when its transmitting. Also the overbleed is likely a symptom of it starting to desynch.

Vision runs out long before the edge of your screen. Requiring a change in focal point. This is the same condition for both setups. Except that on your setup, you can do it in a single view, where as on mine one must soon 'point their nose' in the direction desired to produce the new field. But what does one get? Stare at the gunsight of the pic above, and try to read the gauges. Stare at the wingtip of the other plane and try to determine which gunsight is presented. Have to look back, on both setups. But what else do you get with that setup? A bowed, distorted view of the cockpit from the back seat. And objects at distance far out of scale. Then, consider the OP. Views that are proportional to the front seat cockpit view, optically flat, and easy to read gauges. Outside views are also proportional and flat, to the same 55° FOV as the external view itself. The only catch, is that it requires one to pan to a new view sooner. With a little practice, situational awareness and theater-of-the-mind builds the holodeck, like driving your car, and the scan pattern just updates the global image. A little more work from the 'arcade' setup, but a huge payoff in realism and immersion. Won't know until you try it, long enough to get the hang of it. No supernatural zooming or labels, no warped, backseat views. Bowie

I had black screen too, the plane loaded partially first, then black screen and crashed. I did a repair, reinstalled all my Pimax stuff but it’s still doing it. I’ll try deleting the mission editor folder and try it again. Thanks for the idea.

That might be wrong. There is a maintenance manual that has a section on "blanking" the RWR for use with the radar correctly. At a guess the reversion mode is to turn it off if its not blanked right, and probably wasn't often done right/well IRL by 3rd party operators at a guess after the SU collapsed. Also a story from a serbian pilot that got SPO warning while locking up some allied jet during the balkan wars. Working on it. Actually in Vietnam the USAF didn't have GCI early on over north Vietnam. While the navy did have it with their red crown awacs, and its one of the reasons the Navy did better than the USAF early on. Later the US copied/worked with the Navy on it.

Yep I’m running on the Pimax crystal super too

Well "a few 29's" but yeah. And at least in the gulf and the balkans the F15's were mostly still "cold war" era (ish). But most people don't realize that all the fancy radar modes etc on the F15 only came in the late 80's. So, early on it would have been a bit more challenging for NATO. Not to mention there were only 2-3 squadrons of F15's in europe total. Per soviet doctrine, 29's weren't supposed to fight F15's anyway unless it was a GCI directed ambush. Vipers are another story.

I'm no longer able to export displays while in VR. This is on a new computer, clean DCS install with the latest patch. It could be an issue with the new patch, or just an error on my part setting this all up again. I'm able to export as expected when not in VR. This is my monitor config I'm using in VR. It's the same file I ran with the old computer, before it ran off to college with my son. When not in VR, I use the same file as below, minus the VR_MIRROR section and VR_allow_MFD_out_of_HMD = true What I see on the 2nd monitor, is just my desktop background image. _ = function(p) return p end name = _('Helios') description = 'Generated from compatible Helios Profiles' function reconfigure_for_unit(unit_type) if unit_type == "FA-18C_hornet" or false then FA_18C_CENTER_MFCD = { x = 3303, y = 690, width = 410, height = 390 } FA_18C_IFEI = { x = 2579, y = 773, width = 614, height = 188 } FA_18C_LEFT_MFCD = { x = 2631, y = 245, width = 410, height = 410 } FA_18C_RIGHT_MFCD = { x = 3982, y = 244, width = 410, height = 410 } FA_18C_RWR = { x = 4044, y = 747, width = 165, height = 165 } return end -- _FA-18C_hornet end -- reconfigure_for_unit() Viewports = { Center = { x = 0, y = 0, width = 2560, height = 1440, aspect = 1.77777777777778, dx = 0, dy = 0 } } VR_MIRROR = { x = 0, y = 0, width = 2560, height = 1440 } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center -- Added by Helios Monitor Setup Script Appender VR_allow_MFD_out_of_HMD = true

Just saying… it is easy to see how the F-15 has been the end of many MiG-29’s… and why the roles were never reversed.

Wer das Handbuch aus irgendeinem Grund nicht findet, DCS nicht installiert oder was auch immer. Es ist, wie alle anderen Handbücher, auch in der Dokumentation auf der Webseite zu finden. https://www.digitalcombatsimulator.com/en/downloads/documentation/filter/aircraft-is-mig-29/apply/

So, I think ED got the RWR wrong in the regard that the SPO 15 was not "blind" in the frontal arc, there is a maintenance doc that talks about properly "blanking"/synching the SPO-15 when using the radar. But I think this maintenance tended not to be done by some allied countries (or they lacked spare parts), and the reversion mode just shuts it off if its out of synch. There is also a serbian account of a mig29 pilot that was trying to lock up a western jet when his RWR went off and he was able to evade the missile.

I can confirm what everyone else is saying. Just received my Crystal Super 57PPD. Flying the same missions that OP posted about - Rampagers Mission 3 at night in Syria, the entire HUD and bascislly interior of F18 even with all dimmers turned down to the absolute minimum, there is a white/grey haze around everything. Hurts the eyes to be honest. On the other hand, flew mission 9 or 10 on the V for Victory campaign and everything wasn’t blown out like it was in Syria with the F18… I wonder if it’s the lack of cloud moon lighting along with a bright cockpit (even on minimal brightness with gamma at 1.8). Followed Tallymouses video, using quad views companion, DLSS through nvidia prospector. Everything looks great during the daylight over Syria with the F18 but this mission is a mess without moonlight. Has anyone found a fix? Anything from @Calvin.Pimax?

Can we get this as part of the module setting instead of using the global ones. I use Imperial for all the western jets and want to use Metric for the Mig29... And its a PITA to switch it globally constantly. Thank you for your attention in this matter.

Yeah - pieces of metal can do a long way. But at 20 metres your unlikely to be killed. At 200m there will be zero change of being killed...and a fairly low chance that a stray frag hitting you ...and if it did, you'd get a nasty cut..,or even blinded if it hit your eye. So yeah - absolutely hide when within 200metres...but that's very different to killing every living thing within 20m

Lately, I have been flying in the Marianas exclusively, and I have had no luck with PRMG there. Will try Caucasus.

Does the monster share the same bolt hole mounting pattern to the rig as the regular rhino?

The new fuzing (and skins) is only enabled on single racks not dual racks and by default the single racks open after 1.2 seconds....dual racks dont open so quickly. The OP fuzing doesnt work on the Harrier..I guess that would need Razbam to implement...but am not sure. You can fix this by using the "copy to pylons with the same weapons"....but surely they should default to the same. Rockeye Broken1.trk

I would support an updated Mig21 of any variant. But if a developer like Heatblur was to announce a MIG 23 project instead, I could live with the current Mig21 BIS.

Non credo che il significato che l'AMX può aver avuto per noi o per i Brasiliani, sia sufficiente a giustificare economicamente lo sviluppo di un modulo Full Fidelity

Would be nice to have some official statement from the dev team about status of 1.2. Surprised how quiet it is. Are they all talking on discord or something?

Thanks for the reply at last. Using another USB mouse with macros just for this action looks like a good idea, however in my case it leads another problem: I am on my USB limit and adding another device adds quite some instability. Having a working ejection handle between my legs feels better than a mouse button.

Yeah, I must be getting old or something. I setup all of my aircraft and I absolutely did not remember having to do this for each one. It has been awhile since I bought an aircraft module, so I must have just forgotten. Checked all my aircraft, and there were a couple that didn't have it checked, and sure enough the forces were not correct on them. I can't believe I didn't notice. Thanks for the fix, and if you ever need a copy of the correct dinput8.dll to fix the zoom stutter let me know.

I've launched the replay to see if maybe it was stealth fixed. Nope. Also copying wpt 1 to 36 and launching the bombs in PP mode somehow makes it even worse... But hey, it's marked as reported over half a year ago and soon we can launch an anniversary party for this thread. @BIGNEWY invited. This time I won't go asking on discord why they won't let 3rd party devs deal with weapons.

Так МиГ в раннем доступе. Технически, ещё не вышел, получается