Jump to content

ralgha

Members
  • Posts

    57
  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    DCS, MSFS
  • Location
    US
  • Occupation
    Software developer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. Sadly, this is still broken in the 2.5 "release" version.
  4. 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
  5. 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).
  6. 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!
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. ED broke every campaign in the latest patch - see the following: https://forums.eagle.ru/showthread.php?p=2988016
  12. 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...
  13. 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!
  14. 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.
×
×
  • Create New...