On Tuesday, 30 October 2018 at 10:46:35 UTC, Mike Parker wrote:
On Tuesday, 30 October 2018 at 10:30:48 UTC, John Burton wrote:
I want to do some graphics using direct3d11 on windows.
There are some bindings that I used once before
https://github.com/evilrat666/directx-d
However they are marke
On Tuesday, 30 October 2018 at 10:30:48 UTC, John Burton wrote:
I want to do some graphics using direct3d11 on windows.
There are some bindings that I used once before
https://github.com/evilrat666/directx-d
However they are marked as [discontinued]
While I'm sure they will continue to work so
I want to do some graphics using direct3d11 on windows.
There are some bindings that I used once before
https://github.com/evilrat666/directx-d
However they are marked as [discontinued]
While I'm sure they will continue to work so wouldn't worry about
using this I wonder if there are any other
Am 30.10.2013 17:53, schrieb evilrat:
On Wednesday, 30 October 2013 at 15:18:57 UTC, Benjamin Thaut wrote:
Well we all make problems. Give me a note when you are done with
complete directx bindings as I'm also interrested in having minimal up
to date directx bindings.
Also its a
On Wednesday, 30 October 2013 at 15:18:57 UTC, Benjamin Thaut
wrote:
Well we all make problems. Give me a note when you are done
with complete directx bindings as I'm also interrested in
having minimal up to date directx bindings.
Also its always apperciated to thank you a person
, and then i can clean d3d11 mess i made.
Well we all make problems. Give me a note when you are done with
complete directx bindings as I'm also interrested in having minimal up
to date directx bindings.
Also its always apperciated to thank you a person which invested
multiple hours to tr
On Tuesday, 29 October 2013 at 19:40:40 UTC, Benjamin Thaut wrote:
So I found it. Its actually your fault.
IXAudio2Voice isn't a COM interface. That means it should _not_
inherit from IUnkown. But if it isn't a COM interface it can't
be a regular D interface either, because if it is a regular
On Tuesday, 29 October 2013 at 19:40:40 UTC, Benjamin Thaut wrote:
So I found it. Its actually your fault.
IXAudio2Voice isn't a COM interface. That means it should _not_
inherit from IUnkown. But if it isn't a COM interface it can't
be a regular D interface either, because if it is a regular
Am 29.10.2013 21:26, schrieb Heinz:
On Tuesday, 29 October 2013 at 19:40:40 UTC, Benjamin Thaut wrote:
So I found it. Its actually your fault.
IXAudio2Voice isn't a COM interface. That means it should _not_
inherit from IUnkown. But if it isn't a COM interface it can't be a
regular D interface
So I found it. Its actually your fault.
IXAudio2Voice isn't a COM interface. That means it should _not_ inherit
from IUnkown. But if it isn't a COM interface it can't be a regular D
interface either, because if it is a regular D-Interface it will not
have a v-table layout that conforms with C+
I have the exact same problem with XAudio2 in my own code. Code
compiles and run but doesn't output any sound. I tried your code
but it's the same as mine, runs but doesn't sound.
I'm using in my code the bindings from
http://www.dsource.org/projects/bindings/wiki/DirectX
Can't really understand
On Tuesday, 29 October 2013 at 14:13:40 UTC, Benjamin Thaut wrote:
I also found that for all pp members which take pointers to COM
interfaces. For example the "CreateMasteringVoice"
"IXAudio2MasteringVoice** ppMasteringVoice" member. In D
interfaces are already reference types. So it should r
On Tuesday, 29 October 2013 at 14:13:40 UTC, Benjamin Thaut wrote:
As I'm not familiar with xaudio2 I will not be able to help you
unless you present a example which actually crashes. I don't
think this is a COM issue. Does a C++ program which does the
same work?
C++ example works fine(link
Am 29.10.2013 15:00, schrieb Benjamin Thaut:
Am 29.10.2013 14:45, schrieb evilrat:
On Tuesday, 29 October 2013 at 13:35:11 UTC, Benjamin Thaut wrote:
I already found the first problem with your library.
Your directx modules have module declarations in the form of:
module directx.xaudio2;
but
Am 29.10.2013 14:45, schrieb evilrat:
On Tuesday, 29 October 2013 at 13:35:11 UTC, Benjamin Thaut wrote:
I already found the first problem with your library.
Your directx modules have module declarations in the form of:
module directx.xaudio2;
but they are directly within the src directory.
Yo
On Tuesday, 29 October 2013 at 13:35:11 UTC, Benjamin Thaut wrote:
I already found the first problem with your library.
Your directx modules have module declarations in the form of:
module directx.xaudio2;
but they are directly within the src directory.
You should create a subfolder called "dir
I already found the first problem with your library.
Your directx modules have module declarations in the form of:
module directx.xaudio2;
but they are directly within the src directory.
You should create a subfolder called "directx" and place all your
modules in there so it is actually consist
On Tuesday, 29 October 2013 at 11:47:00 UTC, Benjamin Thaut wrote:
Am 29.10.2013 10:38, schrieb evilrat:
omg, almost a month passed and i even didn't notice it.
after some "research" i'm still don't know what the problem.
some COM
calls works, some fails(probably wrong method calls, and it
no
Am 29.10.2013 10:38, schrieb evilrat:
omg, almost a month passed and i even didn't notice it.
after some "research" i'm still don't know what the problem. some COM
calls works, some fails(probably wrong method calls, and it not crashes
just because same args). now i have half working d3d11 and n
omg, almost a month passed and i even didn't notice it.
after some "research" i'm still don't know what the problem. some
COM calls works, some fails(probably wrong method calls, and it
not crashes just because same args). now i have half working
d3d11 and not working at all xaudio2.
due to
On Sunday, 6 October 2013 at 16:45:59 UTC, Benjamin Thaut wrote:
Am 06.10.2013 07:25, schrieb evilrat:
oh, on the second thought after some tests, i encountered
major ABI(or
should i say MS 'optimization'?) mismatch which requires
almost any
function to be wrapped within C++ code to work, i dou
Am 06.10.2013 07:25, schrieb evilrat:
oh, on the second thought after some tests, i encountered major ABI(or
should i say MS 'optimization'?) mismatch which requires almost any
function to be wrapped within C++ code to work, i doubt it would ever
costs such efforts for me.
so i'm tired off both
oh, on the second thought after some tests, i encountered major
ABI(or should i say MS 'optimization'?) mismatch which requires
almost any function to be wrapped within C++ code to work, i
doubt it would ever costs such efforts for me.
so i'm tired off both C++ and D. and programming in genera
On Thursday, 3 October 2013 at 06:19:27 UTC, evilrat wrote:
i'm trying directx bindings from dsource
(http://dsource.org/projects/bindings/wiki/DirectX)
and encountered problem, when calling swap chain getbuffer it
suddenly crashes. does anyone using it? any help please :(
// Create a r
On Thursday, 3 October 2013 at 11:30:58 UTC, Andrej Mitrovic
wrote:
On 10/3/13, evilrat wrote:
// Create a render target view
ID3D11Texture2D* pBackBuffer;
// C++ version
//hr = g_pSwapChain->GetBuffer( 0, __uuidof( ID3D11Texture2D
),(LPVOID*)&pBackBuffer );
// D version(crashes)
hr =
this. but
as i said
it looks like guid problem.
If you think it is a guid problem you could just open the c++
header lookup the GUID and compare it to the one in derlict
this is not derelict, it's old directx bindings that was part of
winapi bindings i think.
On 10/3/13, evilrat wrote:
> // Create a render target view
> ID3D11Texture2D* pBackBuffer;
>
> // C++ version
> //hr = g_pSwapChain->GetBuffer( 0, __uuidof( ID3D11Texture2D
> ),(LPVOID*)&pBackBuffer );
>
> // D version(crashes)
> hr = g_pSwapChain.GetBuffer( 0, &IID_ID3D11Texture2D,
> cast
Am 03.10.2013 12:47, schrieb evilrat:
On Thursday, 3 October 2013 at 10:08:42 UTC, Benjamin Thaut wrote:
NO I mean are you sure the library paths are correctly set to the
"June 2010 DirectX SDK/lib" path?
all paths are set correctly.
Do you use 32 or 64 bit?
32 bit.
You can get details
On Thursday, 3 October 2013 at 10:08:42 UTC, Benjamin Thaut wrote:
NO I mean are you sure the library paths are correctly set to
the "June 2010 DirectX SDK/lib" path?
all paths are set correctly.
Do you use 32 or 64 bit?
32 bit.
You can get details on crashes inside DirectX by using the
Am 03.10.2013 11:57, schrieb evilrat:
On Thursday, 3 October 2013 at 09:35:46 UTC, Benjamin Thaut wrote:
Am 03.10.2013 08:19, schrieb evilrat:
i'm trying directx bindings from dsource
(http://dsource.org/projects/bindings/wiki/DirectX)
and encountered problem, when calling swap chain getb
On Thursday, 3 October 2013 at 09:35:46 UTC, Benjamin Thaut wrote:
Am 03.10.2013 08:19, schrieb evilrat:
i'm trying directx bindings from dsource
(http://dsource.org/projects/bindings/wiki/DirectX)
and encountered problem, when calling swap chain getbuffer it
suddenly
crashes. does a
Am 03.10.2013 08:19, schrieb evilrat:
i'm trying directx bindings from dsource
(http://dsource.org/projects/bindings/wiki/DirectX)
and encountered problem, when calling swap chain getbuffer it suddenly
crashes. does anyone using it? any help please :(
// Create a render target
i'm trying directx bindings from dsource
(http://dsource.org/projects/bindings/wiki/DirectX)
and encountered problem, when calling swap chain getbuffer it
suddenly crashes. does anyone using it? any help please :(
// Create a render target view
ID3D11Texture2D* pBackBuffer;
33 matches
Mail list logo
