ralgha

No problem. Thanks for sticking with us all these years! I ended up flying the first two missions and had a great time. Well, until I plowed it into the water trying to hit one of those darn speedboats. I'll be back for them next time I get a chance to fly. The new clouds really do add a lot to the experience.

I love this campaign so I went to try it from the beginning with the new clouds in 2.7, but I didn't get very far. I called for ground power on mission 1 in the MiG-15 and there was no response. The F10 map showed Anapa as neutral but the mission editor showed it as red. Huh? Based on this thread I tried adding 10 Russian tanks nearby in the ME. Then Anapa showed up red in-sim and I got a ground crew response. So for some reason, the airfield doesn't seem to have enough red forces around for DCS to consider it properly red. I didn't see any non-red forces around so I'm not sure why, but it seems this mission needs a little help to work again out of the box. I checked the first F-86 mission and the second MiG-15 mission and neither of them had this problem. I also tried creating a minimal test mission from scratch where I just added one cold start red MiG-15 to Anapa, and that worked fine.

Sadly, this is still broken in the 2.5 "release" version.

I found a workaround that will let you fly missions affected by this bug. The steps are here: https://forums.eagle.ru/showpost.php?p=3395192&postcount=4

I discovered that we can actually fix and run these missions ourselves. Here's the workaround that worked for me: Go to your DCS installation folder, then open Mods\campaigns\The Museum Relic Unzip the bad .miz file to a new folder (using e.g. 7-Zip - .miz files are really just .zip files) Open the file called "mission" with a compatible text editor (e.g. Notepad++ or Notepad2) Remove the line from the requiredModules section at the beginning that references "F-4E by Belsimtek" Search and replace all occurrences of "F-4E_new" with "F-4E" Save the file and exit Re-zip the contents of the folder Rename your new .zip file to .miz, give it some name different from the original, and put it in the same folder as the original Launch DCS and choose "Mission" from the main menu Browse to the folder with the campaign missions, pick your fixed mission file, and fly it! (Optional) Doctor your logbook.lua file as described here if you want to continue to use the campaign feature. Personally I think I'm just going to run each mission manually from now on, as this campaign appears to be 100% linear (thankfully).

After playing missions 1-6 in DCS 2.5 before running into a brick wall trying to load mission 7, I tested loading all of the Museum Relic missions and found that the following ones don't currently work: MR campaign 7 MR campaign 9 MR campaign 15 F86 MR campaign 8-2 F86 MR campaign 9 F86 MR campaign 11 DCS displays an error message when attempting to load these missions: "Need modules for load mission: F-4E by Belsimtek" I confirmed that this problem exists in all versions of DCS 2.5 released to the public so far: 02-09-2018 2.5.0.14138 2.5.x Unified Version Hotfix #2 02-06-2018 2.5.0.14044 2.5.x Unified Version Hotfix #1 01-31-2018 2.5.0.13818 2.5.x Unified Version LaunchI hope this will be fixed soon. Missions 1-6 were very impressive in 2.5 in VR. Big step up from 1.5!

In the WWII asset pack there's a German vehicle called Blitz_36-6700A which appears to have broken LOD. This unit is completely invisible until the view gets within maybe 2km or so, at which point it suddenly pops into view. This makes gun runs rather irritating. I tried parking some other vehicles right next to it such as Tiger_I and Kubelwagen_82 and they didn't have this problem. The problem can be observed in VR as well as on a monitor. On a monitor, I paused the sim and pointed the camera at a group of several types of units. I then zoomed in and out and watched these Blitz vehicles pop in and out of view while the other units next to them stayed visible the whole time. I found an old thread from 2011 about this problem that suggests the UAZ was similarly broken in the past. I was able to work around this problem by adding the following line to my autoexec.cfg file (location and syntax described here): options.graphics.Camera.High.lodMult = 2.0Note that it may be necessary to change "High" to some other preset name. The presets and other options are described in DCS\Config\graphics.lua. I tried a setting of 1.5 for lodMult as well but it was only partially effective. The issue was completely resolved by setting it to 2.0. I didn't notice any change in framerate doing this but I didn't do any major testing for that. I also tried changing other options besides lodMult but none of them had any effect. I'm pretty sure I've run into this problem in the past with other ground units but never bothered debugging it until now. Hopefully this info helps someone. And it would be great if this unit got fixed at some point.

I encountered this while flying with two friends on the latest version 2.5.0.14044. The friend who was hosting the mission could see the watchtowers. My other friend and I could not, although we could see the muzzle flash when the watchtowers fired. All three of us were flying P-51Ds on the Caucasus map.

Also ran into this, looking forward to a fix.

Downloading the Nevada terrain took me almost 2 full days with the DCS updater. With Steam it would've been done in 25 minutes. And if I had a monthly cap on my data usage, I would've been even less thrilled about all the data I was forced to upload during that time to other people trying to download the product they paid for.

I reverted to version 1.5.5.59744 and tried mission 7 again. Much better. Got plenty of custom radio messages this time. Thanks for the info, and for the fantastic campaign! Really loving it so far. The mission design and execution bring back fond memories of Wing Commander 2 and Tie Fighter, two of my all-time favorites. But that's a topic for another time.

ED broke every campaign in the latest patch - see the following: https://forums.eagle.ru/showthread.php?p=2988016

I may be having 1.5.5.60338-related problems too. I flew missions 1-5 successfully with version 1.5.5.59744 with zero problems. I then updated to 1.5.5.60338 and attempted mission 6 in the MiG-15bis, but I never hear any of the custom radio messages beyond the very first one that plays right at the beginning. I must've tried 8+ times, with/without radioing ATC, taxiing in different ways, etc. I ended up successfully completing the mission in silence by following hints from the forum, and then listening to the OGG files after, which was unfortunate. I gave mission 7 a try too and didn't get any custom radio messages at all in that one, but the mission seemed to otherwise work normally. I gave up part-way through though. I need to do more testing to figure out if it's really this new DCS version or not that's causing these problems...

Click the download button in the upper right corner of the page to download a zip file containing all files in the folder you're viewing. Then, if you want to save disk space, recompress the files as a .7z file using 7-Zip on max settings with a solid archive. 400 missions are like 300MB zipped, but only 60MB as a .7z file!

I'm also quite interested in flying the MiG-15bis without the gunsight, but not holding my breath as it's a decidedly more combat-oriented aircraft than the L-39 and Mi-8. One can dream, though.

Hmm. The L-39C airspeed indicator has two needles: the thin one is labeled as true airspeed, and the thick one is labeled as indicated airspeed. Are you saying that what this shows as true airspeed requires further conversion? Great point about following beacons out. So simple, but easily overlooked.

Thanks for the reply! Looking forward to the helicopter missions! I did a little research on the speed conversion. From what I read, ground speed is simply true airspeed + wind. If you know your heading, true airspeed, wind direction, and wind speed, it should be possible to calculate ground speed via a bit of vector math. But if the wind direction/speed changes with altitude and there's no way to know what it is, that seems rather troublesome. :) I'm still going to give it a shot, though. Another way of calculating ground speed is to time how long it takes to travel a known distance. Unfortunately this also seems rather difficult to make use of in these kinds of flight plans, but I need to think about it more. Anyway, I think it's great that these missions with their emphasis on timing are making me focus on these problems. One of the best things about DCS for me is learning about and grappling with the challenges faced by real pilots throughout history. It's really interesting! One more topic I forgot to mention before: Regarding the waypoints: They're always right on top of radio beacons, right? Is this a realistic way of formulating flight plans for an A-B route? It seems logical, of course. For an added challenge, I could imagine having a waypoint or two located at some point of interest other than a radio beacon. It might be more trouble than it's worth though. I'm also considering trying to use the radio navigation equipment sparingly, gradually building towards being able to navigate reasonably successfully without it. There are planes that don't have such equipment (as you mentioned with the Dora), plus a real pilot would need to be prepared for that equipment to fail.

Hi! I recently discovered your project and I love it. Fantastic idea! I wanted to give a little feedback: Personally I don't think these are very severe limitations. Even if only the host has failures, it can still be fun for everyone. And a lot of the interesting missions don't even have any failures at all. As for the kneeboard images, this is unfortunate but surmountable. The flight lead becomes responsible for conveying all the necessary info. Realistically folks doing this mission together are probably going to be on external voice comms and can handle it. (At least, that's my use case.) Regarding separate mission files vs. cramming it all into one dynamic mission: I think your solution is fantastic. Disk space is cheap. Complexity is expensive. Complexity kills. Your approach makes it possible to include the custom kneeboard images, which are WAY better than trying to get info via radio commands, and it's easy for the user to choose a desired mission and just jump right in. Btw, these .miz files compress brilliantly using 7-Zip solid archives. 400 missions go from 300MB to 60MB. Regarding landing the Sabre when there's no visibility: I did this once, and it was one of the most exciting and rewarding experiences I ever had in DCS. It was possible because I was on voice with a person who was role-playing as ATC to give me a ground-controlled approach (via precision approach radar, aka F10 on his end). He guided me down by giving me regular updates on course, speed, and rate of descent. As I finally exited the clouds/fog, I was just a little to the right of the runway but I scooted over real quick and landed safely on the first try. What a thrill. If there was a way to script this so as to not require a real person's valuable time acting as flight controller, it'd be a fantastic addition to your missions. Regarding speeds: I've only flown the first two L-39C missions so far, but I'm having a tough time trying to figure out how to use the aircraft's airspeed indicator instead of relying on the assistance you provide via the radio menu in order to find out the ground speed which is needed for navigation. Is it practical in these missions to use the provided info about wind speeds and manually convert from true airspeed to ground speed? If so, how would a pilot in DCS typically go about this? Finally, I just wanted to say thanks a lot, and I'm looking forward to whatever you might come up with for helos or any other improvements to the system. And I hope the folks at ED are paying attention!

Ok, in seriousness, having all the UI in VR is definitely the way to go. It's super annoying to have to take the headset off and put it back on all the time just because the server you were on went down and you have to rejoin, or you need to go and tweak some settings, or whatever. The solution is to make the UI easier to read in VR. Make the plane the UI is presented on bigger so we can turn our heads to read the parts we need at the moment. Keep the plane fixed in space instead of moving forward/backward with head movement so we can lean in if we need to in order to see something more clearly. Heck, maybe even make the size and depth of the plane adjustable, at least in a config file or something. Other games have figured out how to put all of the UI in VR and it works fine. LFS, iRacing, Euro Truck Simulator 2, FlyInside FSX, etc. DCS is close. It just needs a bit more work. For now, we have to use the Force a bit.

You must learn to let go of your reading habits. Your eyes will only deceive you. Don't trust them. Set them aside. Then concentrate, and you will simply know what has been written. This is the true gift of the DK2. It's yours for the taking. All you need to do is reach out with your mind.

What I would like to see most is fixes/completion of what already exists in DCS. For me, this would make more of a difference than new content and new features. But if I had to pick something from that list, it'd be anything BUT dynamic campaigns. *yawn*

Just experimented a bit with DK2 and DCS 1.5. It crashes about half the time on loading a mission, and always when exiting a mission. I had to turn off vsync in the DCS settings which makes no sense as frame timing should be managed automatically when the Rift is being used, but whatever. I was able to run with high settings but got some judder sometimes. I turned down visibility range, turned off HDR and shadows, seemed to help a lot. Very smooth for the most part, even around cities. Tried multiplayer and that worked. F10 shows airfields and players but that's about it - no way to see airport layout. Running Windows 7 64-bit, Oculus runtime 0.7.0.0, NVIDIA driver 356.04, 2x GTX 780 (SLI disabled for DCS).

I just tried this with the DK2. It was cool. I watched from the back seat as two L-39's took off together, flew in close formation for a while, then finally collided. The biggest problem I ran into was network lag. When things were smooth it was fine, but there were periods of lagginess that got very uncomfortable with the plane bumping, jerking, flipping, and warping all over the place. Thankfully the server allowed external views so I switched to F2 when that happened. You don't want to be sitting in someone else's plane in VR when lag hits.

I was on a server with a couple of people and we all experienced this problem around 30,000 feet. But since it was multiplayer, we couldn't hop in the other seat to realize it was happening because the GIB passed out. Nice to know the reason, thanks!

In case anyone is wondering why they still can't talk to ATC even when selecting these channels, only one of the missions that comes with the L-39C, "SM-L39C-One Pass, Haul A--.miz", has these frequencies programmed into the channels. In order to get this working for the other missions, it's necessary to open the mission in the mission editor, select the player aircraft, go to the radio settings, program each channel frequency, save the mission, and use that modified mission.