Digital Workshop

At work I create pubs with Opus v7.04 in Windows 7 and they test and publish just fine.
At home, where I like to test ideas, I find that in Windows 10 (just installed) things fall over.

In preview mode page one won't show unless I move the scroll wheel.
Button to page two then shows elements of both pages superimposed, so unusable.

Anyone else having issues?

Hi Mac,

In Evolution, Stephen has posted that his Windows 10 upgrade on one machine is causing similar issues that he thinks is related to this problem MS is having with Nvidia graphics drivers.

Another of his machines, like my W10 with Intel drivers works fine.

Probably not connected but Opus is now on version 7.5 and includes lots of major fixes especially for HTML5.

</mack>

my graphics adapter driver is Intel HD Graphics 4000. Windows says it is up to date.

I find that if I apply an on show transition on each page then display is just fine. Without the transition only partial or no display occurs.
At least it seems to be a workaround.

Just been back through Stephen's post and his machine with Nvidia also has the HD4000 graphics which he says didn't work. Mine is just the HD3000 model - so looks like the newer version might be the problem.

Have you check dxdiag to see if it's reporting errors?

</mack>

From my Evolution posting:


This is the first replication of the problem with Win 10: based on this new info, appears to be connected to the Intel HD 4000 driver (my machine with the Opus preview black screen problem has Switchable graphics cards between Nvidia GT 640M and a default Intel HD 4000). All drivers are up to date for my Win 10 upgrade installation.

Changing the graphics setting, to use the Nvidia card to run Opus, however, does not fix the problem. Wonder of Opus preview mode is set by its code to use the default graphics card or it makes use of a preview browser that employs the default card?

I am not on Windows 10 yet, but expect I will be someday... or maybe just for testing.

In any case, I came across this page from Intel:

http://www.intel.com/support/graphics/sb/CS-034343.htm

Maybe it will help some folks.

Hi Larry,

Thank you for the suggestions. I have been updating the drivers regularly, but this so far has not fixed the issue.

BTW, since the private messaging is no longer available on the forum, and I had recently wanted to write to you "off-line," can you dig up my old email address that hopefully you have kept somewhere and send me your new email? Your old email that I used a while ago no longer seems to work.

Best Wishes,

Not sure how accurate that table is - I'm running a Sandybridge i7 with HD3000 graphics and W10 and Opus 9.6 work fine - but shouldn't according to that grid.

BTW, anybody looking to check their system specs can type dxdiag into the Search Windows box on the taskbar.

</mack>

Mack,

Probably intel has not contracted someone for the "Gig" to update the table?

I found some irate end-customers discussing same or similar issues -- 5 pages as of Nov 2015. There might be some useful, heads-up nuggets of info there. But it is difficult to read through the discussion to get the small bits of what IT departments and users face.
ETA: https://communities.intel.com/thread/61 ... 0&tstart=0
>> One mentioned success with 3rd-party drivers (Leshcat).
>> Post by zeqzy Sep 20, 2015... says "try adding the intel HD 3000 to the 3500 driver .inf if the HD 3000 code is still present in the driver this will work".
>> Another guy confirms Stephen's issue with nVidia and Intel HD graphics sets having conflicting needs --- by Prometee Aug 7th. "problem is that this driver use WDDM 1.2 and not 2.0 like the second NVIDIA graphic card driver, this difference make this two drivers incompatible."
>> Next post/reply there, says 'success' with wddm 1.3 and the 2.0. ???

>> more... palmiris Nov 19 observes:

Mackavi wrote Mack, apparently and according to Ancestry dot com, you have a Wizard in your genes.

Larry

Larry

So if we build something in OPUS, will it run in Windows 7, 8 or 10? Obviously old OPUS executables maybe a problem if clients upgrade (LOL) to Windows 7, 8, or 10. What have you found?

I don't want to update a client's annual project IF they are going to have multiple problems with non HTML projects.

Windows 10 will only be a problem if your endpoint is running the Intel HD Graphics 4000 Chipset.
It's a fact that this does not work with Opus, I have tried every conceivable solution to no avail...the only worry is that it's is a very poular chipset..so your chances of getting hit are quite high.

I have had some debate on this on the advanced forum and the consensus here seems to be that it is Microsofts fault...like they will ever care about Opus ...anyway...let's hope that the chipset and problem goes away...but I fear Opus may do before it does.

There doesn't appear to be an answer. I have a large corporate estate running this chipset and have had to pull away from Opus and look for an alternative product, sadly.
i need this fixed but see no resolution. The business wants Windows 10 more than my application.

Does that mean last week's upgrade did not fix the problem? It was supposed to be one of the aspects covered - but nobody has feedback.

</mack>

What upgrade are you talking about...I have been running 9.6 for some time...is that supposed to work?
If not, where can I get this recent update?

No, we're on 9.75.

There have been several emails, a technical announcement above and I tweeted the update.

</mack>

My apologies...located the email in my junk mail..and I am now on 9.75.

And...It now works perfectly with the HD 4000 drivers on Windows 10. I just needed to republish with the new version.

Thanks to DW for fixing this. It has saved me having to move away from this product..which I am relieved about.