Welcome, Guest
Username Password: Remember me
  • Page:
  • 1
  • 2

TOPIC: v14 "Failed to compile pixel-shaders" on start

v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #151273

  • MrEntomologist
  • OFFLINE
  • Fresh Boarder
  • Posts: 13
  • 2 years, 3 months ago
Hey guys,

Error log attached.

So I've previously been able to run v11 or 12 on this machine fine. I removed that version a while ago. Fast forward to the present, and I install v14 (installation goes fine). Then when I open for the first time I get the above error (screenshot attached). LWKS appears to load everything fine on startup, and then the error pops up at the end.

To clarify: It appears I can use LWKS - however I've only tried importing some .MOV files taken on a DSLR and LWKS doesn't seem to want to work with them so I understand I will need to convert with EyeFrame first. Just wondering if that error will have any impact on my ability to use the software?

Things I've tried:
- Reinstalling LWKS as admin (making sure to remove all files in the documents folder such as license etc, and removing the Lightworks entry from the registry)
- Updating DirectX through the MS web installer
- Updating DirectX9 specifically
- Running as admin, running in compatibility mode
- Updating GPU driver

My hardware
Windows 10 Pro 64bit
Intel i5 3570k @ stock
Asus P8Z77V-LK
8GB DDR3
Sapphire 7970 3GB @ stock
Xonar DGX Sound card
Samsung 840 SSD (System drive, OS + LWKS installed here)
2x 1TB WD Hard Drives

Bonus: How do you exit the app from the project screen (like in the screenshot)? I have to end task because I can't see an obvious way to exit...

Thanks for your time!
Attachments:
  • Attachment This image is hidden for guests. Please log in or register to see it.
  • Attachment This attachment is hidden for guests. Please log in or register to see it.
i5 3570K | Asus P8Z77-V LK | 8GB G.SKILL DDR3 | Sapphire 7970 3GB | Dell U2412M | Samsung 840 120GB | 2x WD 1TB
Last Edit: 2 years, 3 months ago by MrEntomologist.
The topic has been locked.

Re: v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #151275

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 20860
  • 2 years, 3 months ago
Hi,

Thank you for the valuable information.

Error.log shows that Lightworks has no access to Direct3D which is part DirectX. I haven't seen this error with V14 and DirectX installed. You won’t be able to use video effects. The only software I know about blocking access of V14 to D3D is Rivatuner with AMD graphics after Windows 10 Creators Update.

Do you run Rivatuner?
It's better to travel well than to arrive...
Last Edit: 2 years, 3 months ago by hugly.
The topic has been locked.

Re: v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #151277

  • MrEntomologist
  • OFFLINE
  • Fresh Boarder
  • Posts: 13
  • 2 years, 3 months ago
Hey thanks so much for the quick response - No I don't run any sort of GPU tweaking software. I tried disabling the Radeon Settings app but same result. I'll try to figure out if something could be blocking access.
i5 3570K | Asus P8Z77-V LK | 8GB G.SKILL DDR3 | Sapphire 7970 3GB | Dell U2412M | Samsung 840 120GB | 2x WD 1TB
The topic has been locked.

Re: v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #151284

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 20860
  • 2 years, 3 months ago
I'm not familiar with it, but dxdiag.exe might help finding issues related to DirectX, at least on OS level.
It's better to travel well than to arrive...
Last Edit: 2 years, 3 months ago by hugly.
The topic has been locked.

[SOLVED] v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #151285

  • MrEntomologist
  • OFFLINE
  • Fresh Boarder
  • Posts: 13
  • 2 years, 3 months ago
FIXED.

I completely uninstalled my current AMD Radeon Driver (v17.4.4) using a utility called Display Driver Uninstaller (DDU) which btw is fantastic at doing clean upgrades for GPU drivers. I then installed the optional update (v17.6.2) through the "AMD minimal setup" and I chose NOT to install the 'AMD Settings' app.

So I'm not entirely sure if the issue was with the driver version or with the AMD Settings utility (I suspect the utility), but it's fixed now and lwks no longer hangs when I click the cross to close the app either. Is there a better way to close the app?

Thanks for your time hugly!
i5 3570K | Asus P8Z77-V LK | 8GB G.SKILL DDR3 | Sapphire 7970 3GB | Dell U2412M | Samsung 840 120GB | 2x WD 1TB
Last Edit: 2 years, 3 months ago by MrEntomologist.
The topic has been locked.

Re: [SOLVED] v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #151286

  • MrEntomologist
  • OFFLINE
  • Fresh Boarder
  • Posts: 13
  • 2 years, 3 months ago
Just so you know: I did run a dxdiag before reporting the issue here but it didn't flag any problems.
i5 3570K | Asus P8Z77-V LK | 8GB G.SKILL DDR3 | Sapphire 7970 3GB | Dell U2412M | Samsung 840 120GB | 2x WD 1TB
The topic has been locked.

Re: v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #151287

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 20860
  • 2 years, 3 months ago
Thank you.

Now we found a second candidate potentially interfering with Lightworks D3D interface: AMD settings app (or the driver iteslf?).

Have fun!
It's better to travel well than to arrive...
The topic has been locked.

Re: v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #151426

  • MrEntomologist
  • OFFLINE
  • Fresh Boarder
  • Posts: 13
  • 2 years, 3 months ago
The error is back

Strange that it was gone for a short time - I didn't make any changes to software in that time. I'll try disabling various processes and see what happens.
i5 3570K | Asus P8Z77-V LK | 8GB G.SKILL DDR3 | Sapphire 7970 3GB | Dell U2412M | Samsung 840 120GB | 2x WD 1TB
The topic has been locked.

Re: v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #151429

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 20860
  • 2 years, 3 months ago
Keep us updated.

Does error.log show the same symptoms?

D3DShaderEffect::load( C:\Program Files\Lightworks\Shaders\resize.fx ) : compiler error 8876086c
It's better to travel well than to arrive...
Last Edit: 2 years, 3 months ago by hugly.
The topic has been locked.

Re: v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #151430

  • MrEntomologist
  • OFFLINE
  • Fresh Boarder
  • Posts: 13
  • 2 years, 3 months ago
OK I think I've put it to rest now. I reverted to a previous GPU driver (Radeon Software 17.2.1). I double checked the error log and it's error-free.

Whats puzzling is that I seem to be the only one who had this issue - I couldn't find it mentioned anywhere else, although the specific error code listed in the error log has popped up all over the place.

Can anyone confirm that they are using the latest AMD GPU driver with no problems?
i5 3570K | Asus P8Z77-V LK | 8GB G.SKILL DDR3 | Sapphire 7970 3GB | Dell U2412M | Samsung 840 120GB | 2x WD 1TB
The topic has been locked.

Re: v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #152032

  • MrEntomologist
  • OFFLINE
  • Fresh Boarder
  • Posts: 13
  • 2 years, 3 months ago
Update: The error came back because Windows 10 automatically installs new drivers. The solution (for Win10 Pro users) is to use the group policy editor as described here to prevent installation of GPU drivers. Simply remove the policy to manually update the GPU driver when you want to test a new version.
i5 3570K | Asus P8Z77-V LK | 8GB G.SKILL DDR3 | Sapphire 7970 3GB | Dell U2412M | Samsung 840 120GB | 2x WD 1TB
Last Edit: 2 years, 3 months ago by MrEntomologist.
The topic has been locked.

Re: v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #152079

  • mediaDS
  • Pro User
  • OFFLINE
  • Platinum Boarder
  • Posts: 752
  • 2 years, 3 months ago
Or you could use O&O ShutUp10 (or similar tools) to disable driver updates of Windows 10. Please feel free to use the search maschine of your taste for a download link (I assume providing a direct download link could be seen as advertisment or as a link to malicious software and may not be allowed here).
Windows 10 Pro • Asus Z170 Mainboard • Intel Core i7-6700K Skylake, 4 x 4.20 Ghz • 32 GB DDR4 Memory • Noctua Cooling system • Nvidia GeForce GTX1060 6GB DDR5 • Blackmagic Intensity Pro • Samsung SSD 840 500 GB (Data) and 250 GB (System) • 30 TB Asustor NAS (Media) • LG 34UB67 21:9 Ultra-Wide Display 34" @ 2560x1080 • Logitech Bluetooth K810 and M557 • Wacom Intuous Wireless Graphic Tablet • Contour ShuttleXpress • APC Back-UPS 1400VA
Last Edit: 2 years, 3 months ago by mediaDS.
The topic has been locked.

Re: v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #152097

  • MrEntomologist
  • OFFLINE
  • Fresh Boarder
  • Posts: 13
  • 2 years, 3 months ago
Looks like an interesting tool but I only needed to disable automatic gpu driver updates, which can be accomplished pretty easily in the group policy editor.
i5 3570K | Asus P8Z77-V LK | 8GB G.SKILL DDR3 | Sapphire 7970 3GB | Dell U2412M | Samsung 840 120GB | 2x WD 1TB
The topic has been locked.

Re: v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #152098

  • mediaDS
  • Pro User
  • OFFLINE
  • Platinum Boarder
  • Posts: 752
  • 2 years, 3 months ago
Well, I'd advise to disable driver updates all together. Especially if you use new drivers which should never be changed by a faulty windows update (as happened in the past).
Windows 10 Pro • Asus Z170 Mainboard • Intel Core i7-6700K Skylake, 4 x 4.20 Ghz • 32 GB DDR4 Memory • Noctua Cooling system • Nvidia GeForce GTX1060 6GB DDR5 • Blackmagic Intensity Pro • Samsung SSD 840 500 GB (Data) and 250 GB (System) • 30 TB Asustor NAS (Media) • LG 34UB67 21:9 Ultra-Wide Display 34" @ 2560x1080 • Logitech Bluetooth K810 and M557 • Wacom Intuous Wireless Graphic Tablet • Contour ShuttleXpress • APC Back-UPS 1400VA
The topic has been locked.

Re: v14 "Failed to compile pixel-shaders" on start 2 years, 3 months ago #152099

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 20860
  • 2 years, 3 months ago
I believe group policy editor "gpedit.msc" isn't included in Windows 10 Home edition. It is downloadable/installable afterwards, but O&O Shutup seems to be an easy-to-use alternative.
It's better to travel well than to arrive...
Last Edit: 2 years, 3 months ago by hugly.
The topic has been locked.
  • Page:
  • 1
  • 2
Time to create page: 0.42 seconds
Scroll To Top