Those parameters are not supported on multisample textures in the
first place (basically, GL mandates ARB_sampler_objects for those).
The combination COND_NP2 + ARB_texture_multisample is not expected to
happen without wined3d configuration overrides.
On Windows this behavior is hardware dependent. Setting instance_count
to 0 makes all our d3d versions consistent in this regard and avoids
triggering the FIXME() in wined3d:draw_primitive_immediate_mode().
Which is really what it means nowadays: resources created by the
CS. It has mostly implications WRT thread safety.
In particular, the flag doesn't mean that the resource doesn't
participate in memory accounting (that was split into
WINED3DUSAGE_VIDMEM_ACCOUNTING by
723cd0a4ae), nor that it isn't checked
for Reset purposes (we use parent == NULL for that).
Previously, SetupDiGetINFClassW read INF files with
GetPrivateProfileString, which does not substitute %strkey% tokens.
This caused device installation to fail for devices which had driver
INF files using %strkey% tokens in Version section.
An example of such device is Vernier LabQuest Mini (08f7:0008) for
which Vernier's LoggerPro application includes a driver.
The INF file in question adds a new device setup class and has
following entries in Version section:
Class = %ClassName%
ClassGuid = %DeviceClassGUID%
Strings section includes following entries:
DeviceClassGUID = "{6B8429BF-10AD-4b66-9FBA-2FE72B891721}"
ClassName = "VST_WinUSB"
Previously, when LoggerPro was installed and LabQuest Mini was
hotplugged, device installation failed with the following error:
fixme:setupapi:SetupDiGetINFClassW failed to convert "L"%DeviceClassGUID"" into a guid
This caused GUID_NULL to be used and Class was not set to the registry
for the device.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56579
This patch fixes a regression in comparison with SLTG generator in wine-staging,
and allows oleview.exe from PSDK correctly load SLTG typelib generated by widl.
Signed-off-by: Dmitry Timoshkov <dmitry@baikal.ru>
Motor City Online apparently checks for a debugger by setting this flag and then
intentionally causing a page fault. If no debugger is present on Windows, the
subprocess simply dies without spawning any crash dialog. This patch emulates
that behaviour, suppressing a (harmless) crash dialog from winedbg.
This may result in legitimate failures no longer triggering a winedbg crash
dialog, if other programs happen to use SEM_NOGPFAULTERRORBOX, but the winedbg
crash dialog cannot be relied upon anyway.
