RpSPT

This was really waited feature from me. Have been struggling to find targets before that are close by. No more unnecessary circling and nose pointing. Made a fast video but it's a bit choppy.

The coordinates for PP are a bit odd and off. Is there a reason why three of them hit the same boat group and only one is on the closer group that has four boats? Tested in editor where the bombs hit in active pause mode, because there has been some confusion about the coordinates given in these campaign missions. I played trough the mission before and all targets were destroyed with these coordinates though.

Changing the coordinate system seems mandatory if not just finding the target from F10 map and then zooming there with TGP. The coordinates do point close to the target. As seen in that video and this picture that just made from the mission area 1) Select A/C in HSI data page 2) Change format 3) Coordinates given in mission will work now if make a new waypoint 4) TPG shows different numbers than waypoint now, but you get the target here in mission Edit: This image is took from mission editor. Pay no attension to waypoint number that happens to be 2 in the image. Also no target is show because of this.

I think they want us to have FLIR on the target that is waypoint 3 and also fly close to the target when dropping. The flight is saying on radio including FLIP when they are turning in. I skipped using the FLIR before the drop because thought it might override the gps on bombs and took it safe. Have to verify if that is the case actually, because haven't dropped PP mode in a long time before this mission. Edit: PP coordinates on bombs don't get overridden by choosing waypoint as a target, so it's safe to do so.

The one mission where didn't feel the need for refueling with plenty of fuel left has bugged ending on it of course. The AI goes to tanker when checked F10 map after landing. Fixed by editing logbook to load mission 11 and added kills and score to mission 10.

Try get in air faster than him.

Is there any penalty if say unable to find the target enemy boat? I selected it accidentally but had to restart mission because it opened fire on me and CMS didn't cut it. Finished on next try with the correct radio call. I actually like that there's a need for refueling in many missions. Makes it more real. And it's not that hard with correct length stick. Played this eight mission from the new user-file and spawned correctly on the start.

You can edit logbook.lua to load "R1 M03 ALT B.miz" instead the normal mission to get into second refueling. You might have to edit the end score afterwards if interested in keeping all the score. I got trown into mission 4 after exiting the mission so had to do a little bit more editing there, but that can be fixed too if it happens. Posted fix into here: https://forums.eagle.ru/showpost.php?p=4464785&postcount=9 So in your case there is no mission 4 yet. Just change the mission 3 name a little.

Maybe the manual or this missions briefing should say that "enabling GUARD" means GRCV in coms, it seems that other missions have it enabled from start. This mission 5 is confusing if not enabling guard because you need to be also listening this third channel (GUARD) that is listed in kneeboard so some might try to change channels to it on this mission 5. The after join prompt for changing radio channels worked for me. And wingman AI scripting worked trough the mission correctly.

It seem's ALT B is on the second refueling, at least there was a prompt again for save. But continued flying this M03 ALT A mission and finished back to carrier and got the mission success. No problems other than AI jettisoned on refueling and also crashed not landing to carrier. There was some other AI Hornets on the runway but luckily they were just enough out of the way that could land my self. Next mission loaded mission 4 normally so that workaround can be used.

Wish had read this before decided to take a break and shut down DCS on mission 3 after refueling. Well there is a fix. Edit logbook.lua found in Saved Games folder. You might want to make a copy of this file before doing anything else. Open the file in Notepad++ Scroll down to Raven one campaign Find where it says mission 4 but don't delete it yet. Instead delete all that says mission three that is already played: [3] = { ["datetime"] = "XXXX 2020", ["agKills"] = 0, ["aaKills"] = 0, ["result"] = 60, ["deathsCount"] = 0, ["stage"] = 3, ["mission"] = "R1 M03.miz", }, -- end of [3] Now you still have where it says mission 4 Edit it to look like this: [3] = { ["stage"] = 3, ["mission"] = "R1 M03 ALT A.miz", }, -- end of [3] Save the file and go play the campaign from mission that loads from behind the tanker. I don't know what is ALT B version of this mission though. Maybe the devs can tell. If you want to fly from beginning then write "R1 M03.miz" instead. No idea if anything brakes by playing this ALT mission instead of mission 3 from beginning.

I can tell something from using XR-1. The image is so sharp in the center that it's like putting real eye glasses on and watching real instruments. It looks more real than usual HMD's because it takes away the aliasing in the image. The center image is rendered as a separate view which causes the LOD's to be on higher fidelity than the side image. It's a bit strange effect when houses pop up in the center view on far distances. This center image can at least fit Hornet displays in the sharp area. Overall combined FOV is weak. When in Hornet cockpit and watching down to the center display can't see anything outside from peripheral view because the image is cut just barely to the sides of the cockpit window. Also the sides are blurry but maybe it's more because the center is so sharp so it appears worse than it actually is. After using Varjo it's kind of hard to adjust on bad quality in consumer HMD like Index. But I would not buy one for home usage yet. It need's better fov and side clarity. At least they used to be trying to achieve center image that would move to where ever eyes are pointing. That moving sharp image if combined with high FOV would be something worth buying, but who knows when it will happen.

In this video the i5-10600k is clocked into same performance and even over i9. There are also older models on the same charts to compare. Btw don't confuse the i9 -X model to the new one. But if buying CPU now at least I would like it to have more cores for longevity. If only using computer for DCS this i5 with high speeds would be a good buy. My old i7 doesn't go high at all, and even if it did on that test the 5.1 Ghz i7 is often even behind i5 9600k stock.

i9 9900K vs i7 8700K have big difference in same quick mission both with Index and VR preset. But these computers also have different GPU so not 100% sure how it affects. RTX 2080Ti vs GTX 1080. I have i7 6700K/GTX1080 myself and the GPU is maxing at 70% and most of the time even at lower usage in VR and custom settings. So would like to buy a new CPU but also would like to wait for Ryzen 4000 series. But even those Ryzen's are basically same old CPU's than before and they are even changing the socket after them so don't know if actually want to buy anything. New GPU's are also coming so not going to buy 2080Ti anymore. Could still upgrade my CPU first while waiting. There are rumors that the LGA1200 sockets are to be used also in upcoming Intel CPU's. But I don't think I would change to the possible upcoming CPU, if I buy new i7 or i9 now, even if the socket was same. CPU is more expensive part than MOBO anyway. But then I tried playing the new SuperCarrier and fps is 20 on deck ugh. So can I actually wait to buy a new CPU. This is too hard. I could say that there's no proper real missions in DCS for Hornet anyway so why bother.

Pressing space-bar seems to select and was able to save the log that way.

Analog axes really are only usable for large movements with Skhval. Have to use castle switch for small adjustments. Not only because of the deadzone but the Skhval is missing acceleration that the digital control has which is why digital is better in small adjustments. The camera seems to follows the thumbstick with infinite speed. This can be tested with any analog gamepad if not having one on the flight stick.

Finally finished Black Shark Deployment and Medvedev campaigns in VR which I started in december. I have been using Oculus Rift CV1. I have also tested with Vive for some amount of time, but Oculus image is better in terms of reading hud and seeing far away targets. Did not use target enlargement and mainly kept labels of. There are couple of missions with lots of zu-23 where had to turn labels on. Zu-23 are nearly impossible to spot in VR when it is getting darker. Tips and notes: -Flying is easier in VR as it is easier to notice distances and to observe in which direction you are moving. -Used a lot of AI reconnaissance to spot targets before going in. -After reconnaissance stayed atleast 4km away from the spotted enemy AA and tanks. -Used AI wingmen a lot to destroy AA, like those zu-23 which are hard to spot. -Tanks and other bigger vehicles are quite easy to spot with Shkval from far away. -Moving helps avoiding enemy missiles from tanks and bmp completely, so recommend moving all the time. Just not in straight line towards the enemy. -If there is a laser warning going on then turn away if not currently destroing the source of the laser. Use AI reconnaissance again if needed to spot the enemies. -Month of a year were wrong in missions so in Medvedev campaign when the winter comes it was all green but with snow coming from the sky. -Last mission in Medvedev campaign got stuck in AI helicopter not landing to the stadion. Could not get the 100% finnish. I have played these campaigns atleast twice without VR in the past which helped a lot in knowing how to win on all missions. Playing in VR was good experience, and can not fly Ka-50 without VR anymore. The game just is not very good outside the handling of the helicopter. AI is bad and terrain graphics are dated. Some of the mission are very unbalanced, and there are couple of missions where friendly ground forces are suicidal which you are supposed to defend. Still had alot of fun in many missions, especially in those where got to destroy multiple T-72 tanks with four helicopters. It was cool to sometimes just follow and watch AI wingmen attacking and maybe shoot couple missiles yourself staying close. Not sure if would recommend playing trough these campaigns in VR if never flown Black Shark. Resolution is not the best, but it is all doable and even enjoyable with current tech VR.

So this is not a bug. Wonder why ED didn't update their own missions, or am I missing something here? It seems like the weather is still cold in those missions, as the helicopter warns about ice.

Cleanup and repair did not fix the problem. I used this as a guide: https://www.digitalcombatsimulator.com/en/support/faq/709/ I was able to change month for single missions in mission editor and got the winter season textures that way. It is not a proper solution for campaign missions though. Mission month setting seems to be wrong for all missions.

I wonder if missing winter ground textures is some known bug and should I reinstall the game? I have old DCS World installation that has updated many times and on some point winter textures were gone from Black Shark campaign missions and at least from Warthog instant missions. Summer textures are on all maps.

Playing Ka-50 is impossible because the smoke from destroyed groung vehicles lowers the fps to 10 and lower. My computer is i5 2500k 4.2Ghz and gtx 970. Fastest way to test this is to play the mission Battle where multiple ground vehicles get destroyed in couple of minutes. Looking away from the battleground smokes "fixes" the fps. I hope the smoke effects get fixed/changed soon as the only version playable seems to be the original standalone Black Shark 2.

X52 pro stick is connected to throttle with cable and cannot be used seperately.

I dont use keyboard keys as modifiers so I left DCS controls almost unchanged. Only thing that I remember to have been changed was that no more need to press LCtrl when using HOTAS TMS buttons on keyboard. http://forums.eagle.ru/showthread.php?t=98036 I should rewrite my script and check if the loop script that I made back in 2012 works on my current setup to get the script more neat. The good thing about my setup is that it works without having to setup too much after updates. It seems that they made some default setup for Saitek stick so have to delete the Saitek columns after updates but that does not take long. The bad thing about this setup is that every joystick button that uses alphabeth keys had to be mapped within the Autohotkey script. Other way would be to map joystick buttons directly to functions inside game. I dont remember clearly but I think there was some problems about saving the setup properly for later use, and that is why I ended up mapping buttons into autokey script.

Does the stick have force trim? The setup looks good.

Have been using Autohotkey for the same usage since 2012. Altough I never quite fully refined my script as it works as it is. Been using double toggle with both ScrLk and Capslock having to be on to write CDU. Less prone for accidents with double safety. If you make your script in a way that it uses default controls that are set for CDU (LCtrl + LWin + key) you dont have to change anything after updates, unless they change default keys...