All Activity

When starting mission in air, I try to lock target with helmet mode without IRST and here no sound and proper indication on monocle, but on HUD I see what R73 is locked on and I can fire. I guess this is a bug, because before update indication was fine.

Okay I think I have found a workaround: 1 - Choose a STPT that is far away from you and make sure the range is showing 'B'. 2 - Set your AG radar off by choosing OVRD. 3 - Set your desired STPT and perform the attack. If you skip step 1 and you OVRD your AG radar while in 'F' units, your range will get stuck to a constant value and will never change no matter which STPT you cycle to. I think this is a bug now.

Teaser WIP screenshots of winter textures...

You have va switch to release a pair or all of them

The only thing I notice it’s turning behavior. According to charts it should hit sustained 9 G right at 900 kmh, and maintain max G until supersonic speed. Right now it stops maintaining 9 G will before supersonic speed

Wait WHAT? Why? What's going on over there? What images services are not blocked?

If you watch my latest video, I let out the symbology differences much clearer

I'm getting this same issue on Syria at present. Any target with a building as backdrop is effectively invisible to Petrovitch. nullIt's admittedly crude but I include an image of the target area of a (botched) attack run here, from the rough direction of the attack run. Targets on the road or in more open spaces (green)were easily acquired and engaged by Petro. Ones which had buildings behind them, even if not particularly close (in red, that BMP-1 on the right strikes me as a particularly bad example) were not targetable, even at very close range. Somewhat disappointingly, I tried to reproduce this to generate a short .trk - but was unable to. I've had this happen twice over the course of this week in multiplayer, but it works fine in singleplayer, apparently. I don't know if any of that is helpful, but I really hope so, it's been a bit of a drag.

Are you aware how to adjust the range for TD degree elevation? If you go to radar elevation chapter of my latest video there are some Tips for it

Could we please get some confirmation? In the current public build there is obvious huge barometric altitude input, and no evidence of using the laser when bombing. Is this intended (and can more information be given on how to deal with it), or a bug?

hello. not definite though likely to be a DNS issue. can you share two bits of info? one is the output of IPCONFIG/all from command prompt. another is the output of NSLOOKUP www.digitalcombatsimulator.com also from command prompt.

Commands are doubled because Keyboard/default.lua and Joystick/default.lua doesn't match

Yup, latest quaggle installed and no custom But because I had quaggle mod I was not surprised of the double inputs. No problem there for me, that's normal behavior. I'm just surprised to not have any after removing it, where others have. That's why I thought they may have this mod installed also. Whatever, not a big deal.

I wonder if the trim button in the original jet is digital like in the module or rather analog. In one original, easy to find flight manual (would attach, but not sure if there’s a copyright or not) there is a side and top view of the stick on page 1-65 figure 1-30 which shows a thin stick-like attachement which may indicate an analog function. If that’s the case, an option to bind that button to an analog axis might be a solution. Anyone here who has an original MiG-29 in the backyard and could take a quick look?

just a Tip OP , imgur it is blocked in UK now, so UK people see this null

Вот тут да, атмосфера

This is still being tuned by the team; we should have some news soon on this. Thanks.

As told, just let them work on the future F1M model, as there are a lot of new systems to be created.I prefer to have this silence, than incredible announcements with disappointments compared to expectations. I can understand that some of you are eargerly await news, but IMHO, EARGES will release some news when the F1M will be next to release instead of announciating freaking news and releasing an "early acces" module. I think they deserve more encouragement than questions about the time of release of the F1M. Personnel message to the EARGES dev team: Just keep your time to work on the F1M development and bring us an alsmost perfect module as you have done it yet. As an amateur creator in question of development, I'm on your side as it could be hard an difficult to create systems almost from zero. And to make them work fine in DCS. All my thoughts and encouragements to you! And in advance, thanks for all the work done and the future work of this great module.

Ahh awesome! love seeing the progress that everyone is making. Never considered having it laser cut.... might actually look into it. I've printed a few bits, done some designs for panels for the laser cutter and other bits for 3d printing, but i'm no where near this stage. Productive use of my break time at work coming up!

SO I think this is by design, sort of like saying yes, you own it but you forgot to enable the module, if that make sense. If you want to get rid of it in your cockpit, its best to just disable in the Mission Editor and leave it alone in Special Options.

Have you made any customizations yourself? Because, obviously, if one adds the defaults from ED in the Saved Games files, then one would of course have doubled the inputs. The Munkwolf files I use don't have that. Just to check, have you tried the latest Quaggles version? There was a new release after this update. Cheers!

https://magnitude-3.com/downloads/

sliders are set to 0. The final position of the stick is correct, there's just that annoying pull at button release.