kobeshow

https://www.youtube.com/watch?v=8OPEWljAWw8

welp, I checked it again, and the problem occurs if you want to change the size/position of your kneeboard, the specified corruptions are as follows: scripts/aircrafts/_common/cockpit/viewporthandling.lua scripts/aircrafts/_common/cockpit/kneeboard/indicator/overlay_page.lua scripts/aircrafts/_common/cockpit/kneeboard/indicator/objects_page.lua as long as you don't use that function of the kneeboard builder you should be fine, if you did however: disable the function in the kneeboard builder, delete the specified files and repait DCS (like I have to do now AGAIN) EDIT: KneeboardBuilder creates file_original.lua so you don't have to run a repair, delete and rename as needed.

well dang, maybe I have an old version or soemthing? I'll check it again thanks for the heads-up

red side needs M460 back, can you put some private Hueys/Gazelles just for him ??? (;

I think there are also problems with synchronisation when dynamic weather is used in Multiplayer.

I have not had that problem, interesting. Kneeboard builder sadly won't work in multiplayer, it does not pass the integrity check ): Although you might creat your custom kneeboard with it, then after the integrity check tells you which files are "corrupted" you can delete them and do a DCS repair, after that don't start the kneeboard builder again. This way you will still have your custom kneeboard images.

of course the lag itsself does not cause this, that is why I said the lag spike needs to come at the right time (see Bushmanni's comment above).

I don't think there is since there are still some kinks to work out, it kind of works right now but you can hardly call it "precision bombing" (;

I would even go as far as saying that missile performance and netcode make DCS useless for "serious" multiplayer matches. Such a small thing as a lag spike can break your wings in the flanker if it happens at the wrong moment (similar to sudden instant blackout, which also does not happen in SP, only in MP, although it never happened to me after the breaking wings patch since you cannot afford to pull that many G anyways)

yes I pretty much have the same expirience, to quote myself from another thread: "CCRP was more tricky to figure out, toss bombing always throws the bombs way too far, level flight throws the bombs too far, and slight negative and STABLE pitch almost gets the bombs on target." a lot of things can go wrong for CCRP, pulling up and staying level is the least of my problems though.

Hey Deadbeef, As far as I can tell, it is completely client dependent. I don't know where to set the option in the mission editor, and when I tested it on 104th it depended only on what I had set in my options.

Can confirm this bug, happened to me a couple of days ago.

It still does not work properly, or at least not as described in this thread. When approaching the IP: Selecting PI on the PCA, the diamond does not move to the bottom of the HUD, it only moves if you use ZBI aswell. Updating the IP position works (gets updated in PCN), but does not move the target cross to new position After updating the IP BAD/REC/VAL don't turn on in PCN

yes, that was my thought aswell, the ranging for the pipper works but it does not seem to be considered in the positioning on the hud.

I did some testing and found the following: CCIP bombing seems to be always short of the pipper for me, no matter the angle I'm diving at. CCRP was more tricky to figure out, toss bombing always throws the bombs way too far, level flight throws the bombs too far, and slight negative and STABLE pitch almost gets the bombs on target. I have not tried INS bombing yet, maybe I'll post my findings here, but last time I tried it was not working (before TAS patch so might work now). After figuring out the oddities of the different modes I started to get bombs on target with relative reliability. Now I don't know how precise bombing is supposed to be for the M2000C, this behavior might be realistic and intended.

Hi, I recently flew on your server after I saw it in the server browser, it does not always appear and did not for quite some time for me & this thread was not bumped so I thought the server was down, I was very happy when it appeared again^^ I have a question about the race tracks, are the currently turned off? I was showing them to a couple of friends but sadly the triggers did not seem to work, so there were no messages displayed.

I can confirm that there are some issuews with the radio menu. Some times after taking off from an airfield and landing again the radio menu becomes unresponsive, you can still get into the menu with the communication button but the function keys to select any option don't work. (Multiplayer, M2000C) EDIT: found this post which might be related https://forums.eagle.ru/showpost.php?p=2908981&postcount=1

:doh:

I swear the next time we fly I am just going to shoot you down so I don't have to hear about this anymore :smilewink:

Well, idk what exactly your goal is, but if you set up your fight like you have in this sim the Migs should be easy pickings. R27-R cannot even begin to hope to hit anything beyond 20km, you would barely need to pay any attention to a 20-25nm launch. The S530D outranges this missile without a problem, so shooting first and keeping the pressure on should get you in good position for a win. Keep in mind that A2A is a highly dynamic thing and there is no "if X do Z" answer in most cases, but I can tell you from MP expirience that the Mirage has the longest arm in a ~80's setting (i.e. NO AIM120/ET/ER)

2 weeks it is then (;

No worries (;

never said it was a radar altimeter, but I am really sad that you can't adjust your altimeter in the eagle, FC3 functionality is just a big cluster, the flanker has got a radar altimeter and it can adjust the barometric pressure, eagle doesn't have either ...

I know that you can set your QFE for flaming cliffs aircraft now, I found out just over a month ago that it works for the flanker, so maybe the eagle also has the option.

Have not played with the latest patch myself, maybe it has something to do with this: DCS FC3 Su-25. Radar altimeter pointer corrected Su-25. The boom of opened canopy corrected FC3 aircraft. An enabling of cockpit lights at night by default fixed Su-27/33 indication corrected Fixed issue with China a/c radio without audio