Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum
  1. Home
  2. Just Flight
  3. MSFS Products
  4. Avro Vulcan B Mk. 2, K.2 & MRR
  5. 0.1.3 Issues for MSFS 2020 (no disappearing co-pilot for the right sideboard (hotkey) and weird smoke and heat-effects)

0.1.3 Issues for MSFS 2020 (no disappearing co-pilot for the right sideboard (hotkey) and weird smoke and heat-effects)

Scheduled Pinned Locked Moved Avro Vulcan B Mk. 2, K.2 & MRR
2 Posts 2 Posters 60 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Offline
    N Offline
    NinoGZ
    wrote last edited by
    #1

    Hello, I just wanted to state some issues I have at the current version of the vulcan.
    First: over a year ago I wrote the support for the bug (the initial version didn't had that bug) that the copilot won't disappear at the hotkey (I think ctrl+9) to change to the view of the right sideboard. This still has not been fixed.
    Second: the exhaust effects are looking broken like moving stripes, as well as the smoke.
    I'm using the p42 simfx but I deactivated it for the vulcan to test any difference. The only difference is that there is no smoke effect anymore. The heat blur remains the same.

    Maybe you could have a look at those two things 🙂 Thank you in advance.

    1 Reply Last reply
    0
    • MarkM Offline
      MarkM Offline
      Mark
      JF Staff
      wrote last edited by
      #2

      Thanks for reporting the camera behaviour. I have logged that on our internal bug tracker and we'll take a look at a that ahead of the next update to the Vulcan. in the mean time, disabling the "COCKPIT PILOTS" option on the EFB will remove the copilot from view.

      The exhaust effect is not something I can replicate on my end, so I suspect it is a conflict with another product/mod. In order to confirm this, I would recommend renaming your Community folder to something like "Community.old", then creating a new Community folder named "Community" in the same location, and then installing the Vulcan into the new folder. Launch MSFS with only the Vulcan in your new Community folder and then see the effects are appearing as normal. If they are, that confirms there is a conflict with another mod in your ".old" Community folder.

      Hope that helps.

      Mark - Just Flight

      Just Flight Development Assistant

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users