https://bugs.winehq.org/show_bug.cgi?id=39303
Bug ID: 39303
Summary: Cannot copy schematics between different windows /
ltspice
Product: Wine
Version: 1.7.51
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dieter.jurzitza(a)t-online.de
Distribution: ---
Trying to copy parts or an entire schematic between two schematics in two
windows from within ltspice does not work. I can easily select components to
copy, I can copy them within one single schematic, but I cannot copy them
between two different schematics in a single ltspice instance (what works
without issues using plain windows, but who is using plain windows :-))
Thank you for looking into this,
take care
Dieter Jurzitza
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=29052
Bug #: 29052
Summary: Incorrect handling of lit vertices causes models to
render black in The Longest Journey
Product: Wine
Version: 1.3.32
Platform: x86
URL: http://games.softpedia.com/get/Games-Demo/The-Longest-
Journey-161-Demo.shtml
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: octavian.voicu(a)gmail.com
Classification: Unclassified
Created attachment 37430
--> http://bugs.winehq.org/attachment.cgi?id=37430
Patch to fix issue with black rendered characters.
IDirect3DDevice2 and IDirect3DDevice3 handle lighting differently than
IDirect3DDevice7. Specifically, vertices which have colors but no normals (like
D3DVT_LVERTEX or D3DFVF_LVERTEX) should bypass lighting calculations in the
older interfaces. Wine handles them like in IDirect3DDevice7, rendering them
black.
This makes the models in the game The Longest Journey render black. I wrote a
series of tests that I submitted to wine-patches, but they need a bit more
refactoring to go in. Links to relevant patches from the series are below:
http://source.winehq.org/patches/data/80669http://source.winehq.org/patches/data/80673http://source.winehq.org/patches/data/80670
I'm attaching a patch that fixes these issues, but I need to get the tests in
before submitting it. It also needs a bit more thought on how older interfaces
should handle render states that were introduced in later version of Direct3D
(like D3DRS_LIGHTING).
This patch only fixes the issue with the black rendered characters. There is
another issue that makes characters only render partially, which is tracked in
http://bugs.winehq.org/show_bug.cgi?id=11819.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40879
Bug ID: 40879
Summary: Hard coded values at wined3d_private
Product: Wine
Version: 1.9.13
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: super_man(a)post.com
Distribution: ---
I noticed this while looking at wine source code.
http://source.winehq.org/git/wine.git/blob/65d699eb5f7fc151197f3dc9f36499ee…
426 /* Shader backends */
427
428 /* TODO: Make this dynamic, based on shader limits ? */
429 #define MAX_ATTRIBS 16
430 #define MAX_REG_ADDR 1
431 #define MAX_REG_TEMP 32
432 #define MAX_REG_TEXCRD 8
433 #define MAX_REG_INPUT 32
434 #define MAX_REG_OUTPUT 32
435 #define MAX_CONST_I 16
436 #define MAX_CONST_B 16
437 #define WINED3D_MAX_CBS 15
438
439 /* FIXME: This needs to go up to 2048 for
440 * Shader model 3 according to msdn (and for software shaders) */
441 #define MAX_LABELS 16
Is this hard to make dynamic?
What actually is up to 2048 and isnt?
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52
peter <backfire81(a)outlook.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |backfire81(a)outlook.com
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=35802
Bug ID: 35802
Summary: OneNote 2013 installer needs
KERNEL32.dll.SetWaitableTimerEx
Product: Wine
Version: 1.7.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: hberntsen+winehq(a)gmail.com
Created attachment 47798
--> http://bugs.winehq.org/attachment.cgi?id=47798
the trace of the x86 crash
When running the OneNote 2013 installer, it crashes (see log). You can download
the free installer from http://www.onenote.com/Download. The sha1sum of mine is
cca75f8bbeaaa8d4d060c3d9edae28b3e345a82b. The download page forwarded me to
http://www.onenote.com/Download/win32/x86/en-US (so 32 bit) but also the 64 bit
from http://www.onenote.com/Download/win32/x64/en-US with sha1sum
18031525048a5a8f02789e24cb9c5c104ccf6488 crashes with a missing
SetWaitableTimerEx.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=6141
rebe(a)gmx.net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rebe(a)gmx.net
--- Comment #15 from rebe(a)gmx.net ---
Still an issue using 1.9.11 without modifications; app db recommends installing
native libraries.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=1201
Christoph Korn <christoph.korn(a)posteo.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #18698|0 |1
is obsolete| |
--- Comment #42 from Christoph Korn <christoph.korn(a)posteo.de> ---
Created attachment 54954
--> https://bugs.winehq.org/attachment.cgi?id=54954
wine-1.9.13 log
No problem.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=1201
--- Comment #41 from fjfrackiewicz(a)gmail.com ---
(In reply to Christoph Korn from comment #40)
> Still crashes here:
> korn@pc:~/wineprefixes/msgolf/drive_c/Program Files (x86)/Golf$
> /opt/wine-devel/bin/wine --version
> wine-1.9.13
Hmmm would you mind posting terminal output and any backtraces you receive from
the crash?
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=1201
--- Comment #40 from Christoph Korn <christoph.korn(a)posteo.de> ---
Still crashes here:
korn@pc:~/wineprefixes/msgolf/drive_c/Program Files (x86)/Golf$
/opt/wine-devel/bin/wine --version
wine-1.9.13
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=1201
fjfrackiewicz(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fjfrackiewicz(a)gmail.com
--- Comment #39 from fjfrackiewicz(a)gmail.com ---
Is this still an issue in Wine 1.9.13?
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.