Announcement

Collapse
No announcement yet.

Python Plugin Error/Crash with Quixel MegaScans Bridge

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • replied
    Pay attention that I could solve it

    I run on unreal 4.24
    1) Install the Bridge normally, open it as admin (I did it this way but maybe that part is not necessary)
    2) In the Bridge program, look for any texture and put the "unreal engine" box to press the download button.
    3) With this step the third tab of "export" will appear, here is the same as the previous comments explained, you put your unreal, version 4.24 (in my case use this) and the location of the plugins folder.
    * At this point you should not put export.
    4) You go to the folder of your plugins on your pc before starting unreal and you must delete the folder called "support" (This generates the startup problem with the error).
    5) Open unreal 4.24 and the problem will not appear when starting
    6) Inside you will see the Megascans button in your work bar

    This worked for me after many attempts seeing that I created the error in the pluins folder, it should work, luck

    Leave a comment:


  • replied
    Had the same issue. This instruction helped:
    https://help.quixel.com/hc/en-us/art...e-UE4-LiveLink

    Leave a comment:


  • replied
    Delete "UnrealEnginePython" Folder from the engine directory or where you installed it accidently. It will fix the python console issue.
    To install plugin, make sure you have latest Bridge. Click on export settings>Download plugin>Select engine version>Engine folder(It will automatically select plugin folder)>Your Project folder
    Just click export. It should work fine. I hope it helps.

    Leave a comment:


  • replied
    Just in case someone is looking this up down the road like I was, I got this error when I tried installing the Bridge to Unreal plugin into the wrong directory. I chose just the Unreal Engine directory by mistake, but you need to actually set the path to the Engine/Plugin directory. Repathing it and having Bridge install the plugin to the correct directory fixed the problem.

    Leave a comment:


  • replied
    I have this problem, when i open unreal Engine..... Anybody please help me to resolve this problem

    Leave a comment:


  • replied
    No problems on 4.21, however I have it when I did a manual deploy from the git 4.22 lifeline deploy, now I cant get any 4.22 project to start.

    Leave a comment:


  • replied
    Definitely not fixed as it is causing this issue with mine now

    Leave a comment:


  • replied
    Same here Problem still persists.

    Leave a comment:


  • replied
    its not i still got it

    Leave a comment:


  • replied
    This is all fixed now...

    Leave a comment:


  • replied
    Looks like there was an update and i was kinda stoked but the problem still exists. The 4.21 option was pulled form there latest updated. Well one of these days it will work...

    Totinguis your serendipity renders are amazing......

    Leave a comment:


  • replied
    I contacted Quixel support regarding this issue and it is indeed a problem with their plugin. I was working fine with 4.20 and then updated to 4.21 as well as the Bridge version to the latest and started having this issue. Installed on 4.20 and the problem was the same. So if you didn't, avoid updating Bridge for now.
    They told me that they are trying to fix it asap and ship the new version through Bridge. Today there was an update but the problem still persists. Couldn't find a solution. Will try installing manually as pbdarcey mentions.

    Leave a comment:


  • replied
    Please not this issue only arises when the plugin for megascan is installed through the bridge.

    Leave a comment:


  • replied
    I'm experience this issue with 4.21 only. Will update if quixel tells me the fix. 4.20 had no issue with this.

    Leave a comment:


  • replied
    Just bumping this. Did you ever figure out what's going on? It's happening to me too... I've had bridge working then all of a sudden it's corrupting unreal somehow and I have to install.

    Leave a comment:

Working...
X