System: Win8.1 i3 4gb, low I know but just trying to run the editor.
Have uninstalled and reinstalled, same result:
I open launcher, choose new project, select FPS blueprint template, create project.
Project opens, I insert a cylinder, insert a Materials folder in Contents, insert material in folder.
Rename material, double click the material and Material editor comes up.
I right click beside node and type VectorPar in search bar.
VectorParameter shows up and I click on it.
Dialog pops up saying UE has encountered a problem, and I have to close program.
Will now try ver10 and ver 4.8
Same with ver 10
And with ver 4.8
shame, guess I need a different engine till I get another comp
I get “An unhandled win32 exception occured in UE4Editor.exe [3420]”
Fron Visual Studio 2015:
Unhandled exception at 0x00007FF891506BE2 (igdusc64.dll) in UE4Editor.exe: 0xC0000005: Access violation reading location 0x0000000000000047.
If there is a handler for this exception, the program may be safely continued.
This is a known issue with the Intel Integrated Graphics Driver of which igdusc64.dll is a system file. There are two possible solutions to this issue, depending on if you are on a laptop or desktop that also has an Nvidia or ATI graphics card or if it only has the Intel Integrated Graphics Card.
If you have an Nvidia or ATI card:
You will need to go into the Nvidia Control Panel OR the ATI Catalyst Control Center and ensure that UE4Editor.exe is set to use Max. Performance. In other words, you will need to ensure the Editor is running on the Nvidia or ATI card and not the Intel Integrated Card. There are many Youtube videos explain how to accomplish this specifically simply look up Switchable Graphics Card.
If you only have Intel Integrated Graphics:
You will need to download the newest version of the drivers which can be found here:
will fix the crashing and allow you to continue to build lighting.
I should note that other users have reported that Intel (or their computer/laptop manufacturer) is telling them that they do not need an update. If this is the case, please check to make sure that your driver version is below the 15.36.21.64.4222 driver number. (You can see this number in your DXDIAG.) If it is at that driver number and you are still having this issue, please let us know. If not, one user had to force install the new update by downgrading his driver to an older version and then manually installing the driver linked above.