All Activity

There are versions of the RBK-250 with 2.5kg PTAB and RBK-500 with 1kg PTAB variants (PTAB are unguided HEAT submunitions). Anyway, the tests I did were mainly against groups of soft skin vehicles. Against unarmoured vehicles a FAB is more effective than the RBK. In fact, an OFAB-100 was more effective than an RBK-500 (that weighs five times as much). Try it out. This is definitely not the case. The Mk20 is much more effective than the RBK bombs (including the RBK-500 which ways twice as much as the Rockeye).

It makes Me LAUGH some of the workarounds Users have to do just get basic things to work. Your work around has real credibility as you can see in the picture the real live cow even used a ladder to get up on a roof ! I used to create Trains and do lots of tricks with them but got " FLAMED I WAS WRONG AND I WAS JUST USING WORK AROUNDS " I learned my lesson so i do not share anything now. Have the Cows got pet names like " Daisy, Doris, BigNewEee, NineLines" or just id numbers ? Do you put fences around the roof tops to stop the Cows from wandering off and getting hurt before you Vapourise them ?

Download link added to first post.

Ah, I see. No, I use HP RGS for that, or Steam. Sent from my SM-A536B using Tapatalk

This bug is still present I confirm it.

Sorry, bud. I was quite busy, I could not answer.. Well, "Palette" does mean basically all ED has to offer. And what I mean by that is that ED is welcome to invest their resources in areas that other teams like Heatblur already offer and/or will soon be available from ASC. Heatblur had the GPU, ASC will be bringing the "walk around" feature. That's exactly what we need for all modules. For the 29, we'd rather do this faster than slower, of course. Ideally, in one of the next patches. So, I hope we both understand what I meant...and to not get this wrong...I absolutely love the 29 - otherwise I wouldn't bother with it at all. Greetings, bud.

its first time i report a bug and its later fixed for me. But for not for anyone else

i remember!!!

Have you changed anything at DCS? Copying over a loadout or properties of a unit to several other units is as easy as 3 mouse clicks nowadays. How many mods and liveries have you installed?

This. We do this every weekend. 3 of us. Just wish there was more content to use.

ah i get it. are you talking about DCS controller bindings? or hotkeys and macros in the nvidia app?

Humble apologies, I misread that as referring to the video on core parking, vs. your Process Lasso one I see as a link now. Needed more coffee.

The default load out changed in general. It was highly unlikely that 1 load out was copied to EVERY blue Apache. I also have a bug for the active livery showing "default" when there is obviously a different livery being displayed.

Any reason why you're using OpenComposite? DCS is a native OpenXR game so shouldn't be used with that. And yes, Pimax should ideally be used with either the PimaxPlay OpenXR runtime or Mbucchia's Pimax runtime and not SteamVR.

To clarify, the video that was linked about the use of Process Lasso, is about disabling the E-cores per application. Not about anything that DCS is doing on its own. Not saying that disabling the E-cores is the ultimate solution, or the only solution. In my case, the cores weren't parked. But the fps dropped to 3-5 in certain modules in VR. Using the recommendations from the video, disabling the E-cores only for DCS brought the rate up to 45fps. The issue was specific to VR. Without VR, the fps is 100+ even with the E-cores enabled.

Well... I just may have solved the problem. I went back to Open Composite, activated it and disabled Steam VR in the Open Composite option. Activated Open XR and Tool kit programs. Started Pimax Play, and in the Games section disabled in the menus any reference to Steam VR (including aspects regarding the DCS Game Start option) and hit Apply. Then activated DCS from the Pimax Game option (with all the Steam VR stuff off). Held my breath, and to my amazement flew a complete 40 min solo Nav mission out of Maykop from cold start to shut down. Everything worked perfectly!! Therefore, I am assuming the problem is actually with Pimax, (not playing with) Steam VR and something to do with those two that relates to the Mig-29A module. Of course that was only one flight. Will try multiple flights soon and report if all is okay using the above process. Again this whole problem only seems to be a factor with 29A module, all others are fine. As I am fixated on the 29A for the time being, guess this will be the new DCS start norm using the Crystal for me.

Something just randomly changed all your loadouts in your mission? Or is the default loadout changed in general? Have you accidentaly copied the loadout of one unit over to the rest? Or have you modded something? Because default loadout should always be empty, unless you changed it of course.

Su-27SK manual says it happens at 85-95 degrees, I assume this is for high frequency pulse Doppler fighter radars as those are more precise for SPO

Awesome, thank you. I must have missed that update - thanks for the info

For the FC (and now FF) Mig-29 I've always un-mapped aileron trim because it was too coarse and impossible to centre; plus I could count on one hand the times I ever actually needed it compared to the times I accidentally bumped it. As for the pitch axis I do prefer the current gain. The Mig frequently needs gobs of pitch trim (just think of air-starts) so if there are plans to reduce/alter the sensitivity I hope it's optional.

Reinstalling DCS is hardly ever the option. Please provide the information that MAXsenna requested along with a screenshot of the exact error.

@Schlomo1933 Here are two tracks: Rotor brake handle lowered using mouse: the engine starts with rotor brake in lower position. Rotor braked handle lowered using an axis: the engine only starts while rotor brake appears to be in upper position. AXIS.trk MOUSE.trk So, for me at least, the incorrect behaviour you described in OP is still applying. I deleted my axis and rebounded it, but it's still the same result.

Can you please attach your DCS log file for when this occurs again. The log file will get overwritten each time you start DCS so make sure to grab it first.

That's what I was using.