Steph21

Just have tested the update on new open beta version, and issue is gone with the tweak made :thumbup: Thanks a lot Tim, i can now fly with the new pilot :pilotfly:

Indeed, you'll get max G at 440, and max turn rate at 330 Depends of altitude :smilewink:

Baltic Dragon is currently updating mission following changed done during MLO. Manual has been updated to include all latest changes. First training mission has also been updated. It's only updated on Open Beta though, so if you are flying on Stable branch, you can find updated manual and update Training Mission 1 here: https://drive.google.com/drive/folders/1MOyh9LAyJOWVCHaUANa0ZXc6zi_KaM6f

Thanks :thumbup:

It doesn't have a true corner velocity, it has a "corner plateau" which is an airspeed range of 330 - 440 KCAS that produces a good turn rate based on available G.

Here you go. In stable version, seat is not even at max height, i just stopped raising the seat when speed/altitude where aligned on top of the HUD. At max height, they can't be seen anymore. On Open Beta, seat is at max height. We can notice that probe is not visible (just to mention a visual reference) and speed/altitude are not on top of HUD. Same configuration of course (2 Magic and about 1300 kgs of Fuel) Picture at 2Nm: Stable: https://ibb.co/TLW6mqx Open Beta: https://ibb.co/HrzKc06 Picture at 1Nm: Stable: https://ibb.co/dGPrC0V Open Beta: https://ibb.co/x28W33m Picture at 0.5Nm: Stable: https://ibb.co/L9Qgy9N Open Beta: https://ibb.co/PtMnzqY Not sure it illustrates correcty issue mentions by myHelljumper, but we can see the change of height between the 2 versions. Hope it helps

Thanks Tim for the quick workaround on the VTB issue! Cant wait to check it on next update and be able to fly with the new pilot body. Regarding seat height issue for landing, i will try to provide some screenshot comparison tomorrow between stable and open beta versions if still needed.

Probably work also, but you'll have the same issue with head and pilot body alignment. It's like you have your eyes at the back of your head.

It's not ignored for sure, Tim and Baltic updated their part lately. Issue is with situation of Elwood that is the coder working on systems. Seems he mentioned weeks ago that he would put aside the M2000 to work temporarly on other stuff, and we haven't heard about him since. That's why people are wondering if systems are still being worked on currently as some new bugs were introduced with MLO that would need to be corrected (and older bugs too). It was part of Elwood plans to review all reported bugs to make a clear list. Not sure how far he has progressed on this process.

Indeed, lowering the seat doesn't solve the issue, top line of VTB can't be seen properly even at the lower position. Only workaround for user with head tracking device (VR, Track IR,...) is to lean forward (5 cm), hit center view, then lean backward to gaming position. But then, head is not aligned with Pilot body. Not sure what users without head tracking device can do about it. As for seat raised at max at 14° AOA, i can confirm what is mentioned above by myHelljumper. Current default view and seat handling are perfect in Stable version. Current implementation of new pilot body on Open Beta has negative impact on both. This is just objective feedback on new pilot body implementation on Beta branch. Aside from those 2 issues, the new pilot is top notch, clearly the best of all modules i own in DCS :thumbup: Hopefully it can be sorted out before being pushed to Stable branch

Gusto is the historic callsign used by the 2/5 squadron

Yeah i had that in mind too. But then head placement wont match pilot body position. I guess i'll continue flying without pilot body. I'll have to check if it solves other issue mentionned by myhelljumper on max seat high for landing

Cant it be done the other way? Move pilot body 5cm backward ? Then it wont affect the view that was spot on with the rest of the cockpit. Body might 'warp' into the seat ,so not ideal but it woudlnt impacts gameplay. Unless it creates collision issue...

Ok, thanks guys

Thanks for confirmation. Hope it will be fine tuned for next update.

Hi,AIM-9 SLAVE and BORE SMS selection from the Cursor Switch depress function has been implemented. When i click on Cursor Switch depress, it does change from Slave to Bore, but it gets back to Slave automatically when i release cursor switch. Is it designed behaviour ? Shouldn't Cursor Switch depress toggles between Slave and Bore at each click, and not selecting temporarly Bore mode while Cursor switch is depressed ?

Hi Tim, it looks great ! Has defaut head position been moved a bit forward ? As i can't see information on top line on VTB (where is displayed target speed, target closing speed, etc...) anymore with defaut head position. I have to lean backward or move head down. Even when i lower the seat to the max, i still can't see the information properly (partially hidden) Not the case in Stable version. I'm playing in VR Playing Guns Guns Guns instant action mission on Caucasus on Stable branch and then Open Beta can easily show the difference by locking Mig23 at the start of the mission. Other guys having the same issue ?

Not sure what we can expect more, as we only had sign of life from Baltic and Tim lately, and it's all in the change log (updated manual, updated missions, new VR pilot). We haven't heard from Elwood since he mentioned he was working on other stuff.

From F16 changelog: Input for DL switch and MAP switch What does that mean ? New control input available in controls list ? I thought those 2 were not used in F16C Block 50 (mentioned by wags in tutorial videos)

Thanks Baltic :thumbup:

Thanks for the updated Manual Baltic (can be downloaded via link provided on Razbam Facebook until next Open Beta release). I have started to read the newly added infos, on WSC for example. From what i understood it has been validated by coders before manual update release. Regarding the WSC logic with AG Weapon selected on PCA, it's mentionned that pressing WSC Fwd switches system to AG Attack Mode then WSC Aft switch back to Nav Mode with no selection on PCA (as indicated by the arrows). Then a WSC Fwd would enable AA Boresight. That's indeed what is happening in the game as we have to click WSC depress (to leave AA Boresight mode) then WSC Fwd to go back to AG Attack Mode I think one section is missing which is Nav Mode with AG Weapon selected where a WSC Fwd would switch back to AG Attack Mode directly, and not enter AA Boresight like for Nav Mode with no selection on PCA, something like that: https://drive.google.com/open?id=16gJ6JAP663mYTEw6A8LLklV6gNYmPZhZ That at least what i understood from here: https://forums.eagle.ru/showpost.php?p=3975179&postcount=1 Can you confirm behaviour described in the manual (and currently implemented) is the one that has been checked by AdA ? If it's the way it should be, then i'll get used to it (just find it strange to not be able to switch back and forth between NAV and Attack Mode with WSC Fwd/Aft when AG weapon is selected on PCA)

Drift has to be within 15 Nm or you wont be able to validate. But indeed, if within 15 Nm then it automatically update to the correct position of the waypoint.

You can use CCRP with Targeting Pod also, so not only with Steerpoint (which is great as we can't enter new waypoint yet).

I have done it yesterday and had no issue using it. I've just checked p.162 of the manual and indeed all info are in there, especially conditions to be met in order to have it displayed: The M-2000C allows the display of up to 5 waypoints on the VTB screen, provided that the following conditions are met: • They are in the selected radar display range; • They are within the radar aperture limits, i.e. +/- 60 degrees Don't do it at the parking spot. While flying toward your waypoints, set radar display range to maximum value on VTB. Then follow procedure described in the manual. Waypoints should appear if they are within the radar aperture limits, i.e. +/- 60 degrees.

Works fine, select waypoint in prep and click val on pcn. Waypoint has to be within your radar scope/ display range when doing so. You can only display 5 waypoints