Leadwerks 3 Intel HD Graphics Issues

[Denz]

Hi,

Just wondering is the issue with the Intel Graphics going to ever be fixed? I bought Leadwerks 3 Indie Edition when it was in sale around October 31st. I kept getting the 'EXCEPTION_ACCESS_VIOLATION' error each time I try to open a different map, create a new one, or even after a short time roaming around in the editor camera.

 

Just curious if this is an issue with the engine or Intel themselves, because I would love to use this engine I paid for! lol.

 

Thanks in advance.

Regards, Denz.

[Josh]

It worked perfectly with their older driver, then they released a new driver and removed the old driver from their site.

 

I posted here to ask them to restore it:

https://communities.intel.com/message/263496#263496

 

They've acknowledged the bug, but who knows when the next driver update will come out.

 

This is probably the highest priority issue I am working on right now, because it affects about 20% of our users. If I don't get a response quickly I am going to start contacting people inside the company.

 

Not too happy about it. Sorry this is happening.

[nelsoncs]

Have you tried : http://www.intel.com/p/en_US/support?iid=hdr+supportf. ( You probably have).

 

Alternatively, if you own any Intel development products or can establish a customer relatinoship with Intel that includes IPS, you may be able to get an IPS (Intel premier support) ticket. That would be the best way to get some action as the tickets typically are reviewed and as many as possible closed out each Friday.

[Josh]

Okay, I already have a dev account and don't know what permissions it has. I contacted Intel about it. Hopefully we can just add Leadwerks to their OpenGL test applications and not have this happen again.

 

Thanks for bugging me about this!

 

 

Also asked here:

https://software.intel.com/en-us/forums/topic/536093

[Josh]

I'm doing the same thing with AMD here:

http://devgurus.amd.com/message/1306783#1306783

[Josh]

And Nvidia, even though I never have anything to report to them:

https://devtalk.nvidia.com/default/topic/790452/general-graphics-programming/reporting-graphics-driver-bugs-/

[Josh]

Also requested here:

https://software.intel.com/en-us/forums/topic/536108

 

Finally found this:

https://software.intel.com/en-us/forums/topic/532646

[Denz]

Okay thanks, fingers crossed they can fix this soon!

 

EDIT: It's as if Intel doesn't want us to use your engine! lol

[nelsoncs]

I can assure you that is definitely not the case, Intel Wants Leadwerks and all of us to succeed. Intel is a very large ship and one that thus turns very slowly. At each level, there are priorities surrounding a very large work load. Each group, org, manager and code owner has a given set of priorities that drive the daily effort.

 

With this in mind, I made the suggestion to try an obtain and IPS ticket because these usually one of the driving priorities for individual code owners.

 

We also don't know what is required to reinstate the old driver set or configure the newer driver set for backwards compatibility. The simplest changes are bug fixes, but sometimes a design change or specification change is needed which can be a much more involved process (think committees, meetings and so on). In addition, any change to support Leadwerks must be QA'd to make sure nothing else breaks.

 

So, my suggestion has been to try and get our problem into the internal ticketing system for the correct group, keep poking on the ticket every one or two weeks and hang on for the ride. hah.

 

Anyway, I know my comments don't really resolve the issue but I hope they help to give some confidence that a resolution will occur.

[Denz]

I was being sarcastic lol. When I have the time I'll make a ticket.

[Josh]

Intel has pointed me a third party site that has the working driver here:

http://www.guru3d.com/files-details/intel-iris-and-hd-graphics-driver-v15-33-18-download.html

 

They also say the OpenGL problem is fixed and will be included in an update in a few weeks.

[Denz]

Okay thanks so much Josh!

[Denz]

I got my hopes up a little too quickly I think.

 

I still get the same error, but it doesn't do it when I create new maps any more, but for some reason when I was just browsing through the assets list it gave me the error. It's as if it just happens every now and then (which it most likely isn't).

 

Is there an error log or something so I could maybe see of what is causing the issue even with this temp driver fix?

[Denz]

Since I've updated Leadwerks to the beta version I am yet to get the error, which is a good sign, but I'll reply back if I do get the error.

 

EDIT: Talked too soon, I get the error again for some reason just by attempting to move a pivot object up... I also think maybe adding an error log in the directory of Leadwerks would be helpful so if someone does get an error we can know of what is creating an error - if there already is one then pardon me.

[Josh]

No but I can do Intel testing this weekend on these drivers.

[Denz]

Okay awesome.

[Josh]

I am testing with the Intel drivers now and all appears to be fine. I recommend you opt in to the beta branch on Steam. If you continue to experience any problems please create a bug report with instructions to produce the error. The more consistent and reproducable the problem is the easier I can fix it. Thank you.