directpython-general Mailing List for DirectPython (Page 3)

Is there any binging in DirectPython for this? if not,how to do?  thanks~~~

   Elvis

SGksCgpIb3cgY2FuIGkgbWFrZSBhIGZhZGUgaW4gYW5kIGEgZmFkZSBvdXQ/CgpJJ3ZlIG15IG93
biBydXRpbmUsIGJ1dCBteSAicmVjdGFuZ2xlIiBpcyBhbHdheXMgb3BhcXVlLgoKVGhhbmtzLAoK
LS0gCo2hjoGNgaGOoYGBjaGOgaEKU2ViYXN0aWFuIEphdmllciBMdWNhcwpQcm9ncmFtbWVyICYg
R3VpdGFyIEhlcm8K

 


  _____  

From: dir...@li...
[mailto:dir...@li...] On Behalf Of elb
Sent: 12. huhtikuuta 2007 13:08
To: dir...@li...
Subject: [DirectPython] video texture


Hello,

Is there any way to use video texture in DirectPython?
I would like to play some movie file on StaticMesh object, not on Window.
 

Media-object has a getScreenshot() method, but it is usually too slow and
takes too much resources for real-time rendering. It is possibe to render
directly to a D3D surface or texture, but it is not exposed in DirectPython.
If you have some Windows or DirectShow programming experience, you can try
to implement it yourself. There is a sample (Texture3D9) in Windows Platform
SDK which shows how to do it efficiently. It has some special resource
requirements, so adding it to DirectPython can be tricky.
 
--
Heikki Salo

Hello,

Is there any way to use video texture in DirectPython?
I would like to play some movie file on StaticMesh object, not on Window.

  ----- Original Message -----=20
  From: Heikki Salo=20
  To: 'M. Utku Altinkaya' ; dir...@li...=20
  Sent: Monday, February 26, 2007 1:30 PM
  Subject: RE: [DirectPython] Matrix functions






-------------------------------------------------------------------------=
---
    From: dir...@li... =
[mailto:dir...@li...] On Behalf Of =
M. Utku Altinkaya
    Sent: 26. helmikuuta 2007 6:22
    To: dir...@li...
    Subject: [DirectPython] Matrix functions


    Hi,

    Is there any way I can use  D3DXMatrixTranslation, =
D3DXMatrixRotation etc. Also I was not able to find a Matrix class like =
d3dx.Vector, am I missing something or are these not implemented.=20

  It is possible to use all those functions if you have ctypes installed =
(Python 2.5 has it by default). You can use d3dx._d3dx9dll to determine =
which dll you should use. There are several tutorials for ctypes and =
"DirectX for comtypes" (see the SourceForge downloads) has few examples, =
too. Check the directx.util and Frame.SetTransform() for a simple =
example.

  D3DXMATRIX and other structs and functions are not currently exported =
because ctypes is not always available and people often use other =
structs instead (like NumPy matrices, arrays or raw memory). Basically =
D3DX matrix is just a block of memory containing 16 floats so if you =
"know" the alignment requirements and byte representation of a =
structure, you can pass other things to functions which excpect a =
D3DXMATRIX (altough this is little dangerous and not generally =
recommended).

  --
  Heikki Salo
Thanks Heikki, I willl go for native functions at the moment.

 



  _____  

From: dir...@li...
[mailto:dir...@li...] On Behalf Of M.
Utku Altinkaya
Sent: 26. helmikuuta 2007 6:22
To: dir...@li...
Subject: [DirectPython] Matrix functions


Hi,
 
Is there any way I can use  D3DXMatrixTranslation, D3DXMatrixRotation etc.
Also I was not able to find a Matrix class like d3dx.Vector, am I missing
something or are these not implemented. 
 

It is possible to use all those functions if you have ctypes installed
(Python 2.5 has it by default). You can use d3dx._d3dx9dll to determine
which dll you should use. There are several tutorials for ctypes and
"DirectX for comtypes" (see the SourceForge downloads) has few examples,
too. Check the directx.util and Frame.SetTransform() for a simple example.
 
D3DXMATRIX and other structs and functions are not currently exported
because ctypes is not always available and people often use other structs
instead (like NumPy matrices, arrays or raw memory). Basically D3DX matrix
is just a block of memory containing 16 floats so if you "know" the
alignment requirements and byte representation of a structure, you can pass
other things to functions which excpect a D3DXMATRIX (altough this is little
dangerous and not generally recommended).
 
--
Heikki Salo

Hi,

Is there any way I can use  D3DXMatrixTranslation, D3DXMatrixRotation =
etc. Also I was not able to find a Matrix class like d3dx.Vector, am I =
missing something or are these not implemented.

Because of my personal working schedule development of DirectPython is going
to slow down considerably for some time. My contract starts in March and
lasts for 4-5 months and during that time I will have very little time for
other things. Even checking my e-mail can be diffucult, so be patient if you
don't receive answers. However, I can still make bug fixes and add minor
features, but I probably don't have time for anything time consuming.
Fortunately the project itself is in pretty good shape.

I have alredy some plans which I think are useful enough to implement when I
have the time. Given a few months DirectX 10 and Vista should be in a good
shape and maybe nvidia and ATI have managed to get their drivers and
hardware working in a stable manner. The 'comtypes' DirectX interfaces will
also receive more attention. 

The 0.9 (or 1.0, I am not sure yet) should be released at the end of this
month. If you need some extra features or want bugs fixed, there is still
time to report them. 

--
Heikki Salo

 

  _____  

From: dir...@li...
[mailto:dir...@li...] On Behalf Of
Paul Holmberg
Sent: 21. helmikuuta 2007 2:27
To: dir...@li...
Subject: [DirectPython] DirectSound


Hi all,

I am interesting in using DirectPython as an interface to DirectSound, the
end goal being to be able to stream and capture audio in real time using
DirectSound as the sound card interface from python.  While DirectPython
looks promising it appears that the DirectSound interface actually has very
little support.  Is there something I have missed?  And if not then is
support for this planned for the near future? 

Thanks,
Paul Holmberg
 

DirectPython's support for DirectSound is pretty basic and there are no
major plans to extend it. The primary purpose of DirectSound is to play
sounds efficiently, altough it can be used to capture sounds. The biggest
problem is that the DirectSound API itself has not been updated in a long
time and it can be deprecated somewhere in the future. DirectMusic (a
DirectSound "wrapper") has been alredy removed from the DirectX SDK and
altough DirectSound is a pretty good library, it's future is questionable.
Windows Vista already dropped some support and Microsoft has provided some
alternatives like XACT. In short, there are other libraries which are better
suited for sound processing. As a last resort it is possible to use ctypes
or comtypes to directly call the API altough this can be difficult if you
don't have any previous experience with them.
 
--
Heikki Salo

Hi all,

I am interesting in using DirectPython as an interface to DirectSound, the
end goal being to be able to stream and capture audio in real time using
DirectSound as the sound card interface from python.  While DirectPython
looks promising it appears that the DirectSound interface actually has very
little support.  Is there something I have missed?  And if not then is
support for this planned for the near future?

Thanks,
Paul Holmberg

DirectPython 0.8 is now available. Release notes contain all important
information about the update. Some old code can break but fixing
should be relatively simple. 'd3dgui' reveived some major changes and
core interfaces only had smaller updates.

Next version 0.9 will be the last beta vertsion and after it API
should be pretty stable. 0.9 can still make minor changes to the
Effect API, but nothing really big should be coming.

--
Heikki Salo

> -----Original Message-----
> From: dir...@li... 
> [mailto:dir...@li...] 
> On Behalf Of Mudflap Central
> Sent: 12. tammikuuta 2007 19:17
> To: dir...@li...
> Subject: [DirectPython] Does this work with Py2exe
> 
> Hi Heikki,
> 
> Directpy is excelent.  Thank you for making such a great tool 
> for python scripters.
> 
> I have made some adjustments to meshviewer.py to make it use 
> a tkinter interface for .x file and .dds file selection.  
> Makes it easier than using the command line.
> 
> I want to make a .exe file of it.  I have tried py2exe but 
> have had no luck. 
>   Has anyone else had success with this?
> 
> Heikki, is there something structural about the way driectpy 
> that prevents py2exe from making libraries out of it?
> 
> Cheers,
> 
> Mudflap
> 
> _________________________________________________________________
> Communicate instantly! Use your Hotmail address to sign into 
> Windows Live Messenger now. http://get.live.com/messenger/overview
> 
> 
> --------------------------------------------------------------
> -----------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the 
> chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge
&CID=DEVDEV

Using Tk for file dialogs should work. Some things that can cause problems
are .dll's and directories. Make sure that all .dll's and .pyd's are
available and also make sure that paths are correct. They behave little
differently (working directory can be different etc.) with py2exe. 

If you can post/upload your code or error messages in somewhere I might be
able to give better hints if the source is not overly huge.

By the way, your post reminded me that I should write a FileDialog-class for
d3dgui. So I wrote it :) It seems to work ok and I can post it early if you
use d3dgui and have any use for it. It will be in the next release, too.

--
Heikki 

Hi Heikki,

Directpy is excelent.  Thank you for making such a great tool for python 
scripters.

I have made some adjustments to meshviewer.py to make it use a tkinter 
interface for .x file and .dds file selection.  Makes it easier than using 
the command line.

I want to make a .exe file of it.  I have tried py2exe but have had no luck. 
  Has anyone else had success with this?

Heikki, is there something structural about the way driectpy that prevents 
py2exe from making libraries out of it?

Cheers,

Mudflap

_________________________________________________________________
Communicate instantly! Use your Hotmail address to sign into Windows Live 
Messenger now. http://get.live.com/messenger/overview

 


  _____  

From: For...@ao... [mailto:For...@ao...] 
Sent: 21. joulukuuta 2006 15:25
To: Hei...@ut...
Subject: Re: [DirectPython] 3d Text



hello,
   I was able to do what you suggested before I e-mailed you....but the
values I'm getting look something like this:
 
4342335L 4343585L 4341035L
 
I'm not sure I'll be able to use these numbers in an obj file
 
Andre O'Brien 
 

Looks like you found a new bug from DirectPython. That is caused by wrong
interpretation of buffer values, they are stored as 16-bit values but when
converted they are treated as 32-bit ones. This will only happen with meshes
created using fromText(). I will fix this for the next release. 
 
You can extract some values using the struct-module or bitshifts, but the
rest are completely lost. If you are just trying to convert text meshes into
.obj-files, there can better ways to do it. 
 
--
Heikki Salo

 



  _____  

From: For...@ao... [mailto:For...@ao...] 
Sent: 21. joulukuuta 2006 3:30
To: Hei...@ut...
Subject: Re: [DirectPython] 3d Text



hello again,
    I can render the text now (thank you).  I can't rotate the 3d text yet
but I'm sure I'll figure the camera out.  I have access to the vertex and
vertex normals.  I am trying to export this information to a .obj
file....however I don't know how to deal with faces 'f'
 
you need the vertices:
v
vertex normals:
vn
 
and faces:
 
f 1//1 2//2 etc.
 
how do I know what points form a face?
 
Andre O'Brien 
 

Use the index buffer to determine faces. Direct3D meshes are made of
trianglelists (3 vertices per face), so it should not be too difficult. Here
is an example:
 
vbuffer, ibuffer = mesh.getBuffers()
i = 0
indices = ibuffer[:] #Take a temporary copy
while i < len(indices):
    print "Face ",  indices[i:i+3]
    i += 3
 
--
Heikki Salo
 
 

 


  _____  

From: dir...@li...
[mailto:dir...@li...] On Behalf Of
For...@ao...
Sent: 19. joulukuuta 2006 21:02
To: dir...@li...
Subject: [DirectPython] 3d Text


  
Hello,
    I was hoping you could help me.  Is there a way to create 3d Fonts from
fonts located on ones computer?  I see that there are numerous examples of
2-d text.  If you can create 3d text is there a way to access the vertex,
texture, and normal coordinates (x,y,z).
    Any help would be great.  Thank you in advance.
Regards,
            Andre O'Brien
 

It is possible from DirectPython 0.6 onwards. I'll post a little example:
 
        font = d3d.Font(u"Arial", 20)
        textmesh = d3d.StaticMesh.fromFont(font, u"Your text goes here")
        vbuffer, ibuffer = textmesh.getBuffers()
        
        #Take a temporary copy
        tempvb = vbuffer[:]
        for i, vertex in enumerate(tempvb):
            #Go through all vertices
            tmp = list(vertex)
            tmp[0] += 1.0 #Modify x
            tmp[1] += 1.0 #y
            tmp[2] += 1.0 #z etc.
            tempvb[i] = tmp
 
        #Copy temporary list back to the real buffer.
        vbuffer[:] = tempvb
 
This little snippet moves each vertex 1.0-units to all (x, y, z) directions.
You can modify other attributes too, normals would be located at tmp[3-5].
Text meshes have not texture coordinates so you cant access them (unless you
generate them in a shader, but that does not really count). Note that this
is pretty inefficient, vertex shaders are usually used to modify geometry
like this. Of course if you are only generating the data once or modifying
it few times it is ok.
 
--
Heikki Salo
 

Hello,
    I was hoping you could help me.  Is  there a way to create 3d Fonts from 
fonts located on ones computer?  I see  that there are numerous examples of 
2-d text.  If you can create  3d text is there a way to access the vertex, 
texture, and normal  coordinates (x,y,z).
    Any help would be great.  Thank you in  advance.
Regards,
            Andre  O'Brien
 

I downloaded the new version and increased the hardware acceleration level and the samples will now run. I suspect that the level of acceleration was so low that it wasn't recognized. Thanks for your ideas.

Bill
> ------------------------------
> 
> Message: 3
> Date: Wed, 13 Dec 2006 11:04:46 +0200
> From: Heikki Salo <ho...@gm...>
> Subject: Re: [DirectPython] Problem Running Direct.Python Samples
> To: <dir...@li...>
> Message-ID: <457...@mx...>
> Content-Type: text/plain;	charset="us-ascii"
> 
> > A problem running DirectPython Samples. When I try to run any 
> > of the samples with DirectPython I have the following result:
> > xxxxxxxxxxxxxxx
> > Traceback (most recent call last):
> >   File 
> > "C:\Python25\Lib\site-packages\directpy\samples\sampleBasic.py
> > ", line 147, in <module>
> >     mainloop()
> >   File 
> > "C:\Python25\Lib\site-packages\directpy\samples\sampleBasic.py
> > ", line 75, in mainloop
> >     d3d.createDevice(title, u"textures/x.ico", window[2], 
> > window[3], False, CREATE.HARDWARE)
> > RuntimeError: Failed to create a device
> > xxxxxxxxxxxxxxxxxxxxxxx
> > 
> > I take it that the reference is to the following in d3dx:
> > xxxxxxxxxxxxxxx
> > class Frame(object):
> >     def __init__(self, title, fullscreen=False, area=(200, 
> > 100, 800, 600)):
> >         d3d.createDevice(title, u"textures/x.ico", area[2], area[3], 
> >             fullscreen, CREATE.HARDWARE)
> >             
> >         if not fullscreen:
> >             d3d.setWindow(*area)
> > xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > 
> > I was unable to find anything like CREATE.HARDWARE in the 
> > DirectX documentation and help materials. Also, I found the 
> > following sort of code as implementations of the 
> > d3d.CreateDevice( ) syntax and it looks entirely different:
> > xxxxxxxxxxxxxxxxxxxxxx
> > D3D.CreateDevice(D3DADAPTER_DEFAULT, D3DDEVTYPE_HAL, hWnd,
> >     D3DCREATE_SOFTWARE_VERTEXPROCESSING,@d3dpp, D3DDevice) 
> > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Would someone advise if the 
> > problem lies in the CREATE.HARDWARE command, the 
> > d3d.CreateDevice( ) syntax in d3dx, or possible somewhere else? 
> > 
> > Thanks
> > 
> > Bill
> > 
> 
> It is hard to say what fails from here. Do other Direct3D samples or
> applications work properly? What does dxdiag.exe say? What card and
> operating system do you have? Have you updated your drivers?
> 
> You can also try out the traditional way and replace the CREATE.HARDWARE
> with CREATE.SOFTWARE | CREATE.NOCAPCHECK and see what happends. 
> 
> --
> Heikki Salo
> 
> 
> 
> 
> ------------------------------
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> 
> ------------------------------
> 
> _______________________________________________
> directpython-general mailing list
> dir...@li...
> https://lists.sourceforge.net/lists/listinfo/directpython-general
> 
> 
> End of directpython-general Digest, Vol 5, Issue 2
> **************************************************

> A problem running DirectPython Samples. When I try to run any=20
> of the samples with DirectPython I have the following result:
> xxxxxxxxxxxxxxx
> Traceback (most recent call last):
>   File=20
> "C:\Python25\Lib\site-packages\directpy\samples\sampleBasic.py
> ", line 147, in <module>
>     mainloop()
>   File=20
> "C:\Python25\Lib\site-packages\directpy\samples\sampleBasic.py
> ", line 75, in mainloop
>     d3d.createDevice(title, u"textures/x.ico", window[2],=20
> window[3], False, CREATE.HARDWARE)
> RuntimeError: Failed to create a device
> xxxxxxxxxxxxxxxxxxxxxxx
>=20
> I take it that the reference is to the following in d3dx:
> xxxxxxxxxxxxxxx
> class Frame(object):
>     def __init__(self, title, fullscreen=3DFalse, area=3D(200,=20
> 100, 800, 600)):
>         d3d.createDevice(title, u"textures/x.ico", area[2], area[3],=20
>             fullscreen, CREATE.HARDWARE)
>            =20
>         if not fullscreen:
>             d3d.setWindow(*area)
> xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>=20
> I was unable to find anything like =13CREATE.HARDWARE=14 in the=20
> DirectX documentation and help materials. Also, I found the=20
> following sort of code as implementations of the=20
> d3d.CreateDevice( ) syntax and it looks entirely different:
> xxxxxxxxxxxxxxxxxxxxxx
> D3D.CreateDevice(D3DADAPTER_DEFAULT, D3DDEVTYPE_HAL, hWnd,
>     D3DCREATE_SOFTWARE_VERTEXPROCESSING,@d3dpp, D3DDevice)=20
> xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Would someone advise if the=20
> problem lies in the =13CREATE.HARDWARE=14 command, the=20
> d3d.CreateDevice( ) syntax in d3dx, or possible somewhere else?=20
>=20
> Thanks
>=20
> Bill
>=20

It is hard to say what fails from here. Do other Direct3D samples or
applications work properly? What does dxdiag.exe say? What card and
operating system do you have? Have you updated your drivers?

You can also try out the traditional way and replace the CREATE.HARDWARE
with CREATE.SOFTWARE | CREATE.NOCAPCHECK and see what happends.=20

--
Heikki Salo

...so go and download it:
http://sourceforge.net/project/showfiles.php?group_id=158815

Release notes have all important information as usual. Size of the downloads
have grown a little because animated meshes tend to be pretty big even when
compressed. But it is still less than 10mb's.

--
Heikki Salo

A problem running DirectPython Samples. When I try to run any of the samples with DirectPython I have the following result:
xxxxxxxxxxxxxxx
Traceback (most recent call last):
  File "C:\Python25\Lib\site-packages\directpy\samples\sampleBasic.py", line 147, in <module>
    mainloop()
  File "C:\Python25\Lib\site-packages\directpy\samples\sampleBasic.py", line 75, in mainloop
    d3d.createDevice(title, u"textures/x.ico", window[2], window[3], False, CREATE.HARDWARE)
RuntimeError: Failed to create a device
xxxxxxxxxxxxxxxxxxxxxxx

I take it that the reference is to the following in d3dx:
xxxxxxxxxxxxxxx
class Frame(object):
    def __init__(self, title, fullscreen=False, area=(200, 100, 800, 600)):
        d3d.createDevice(title, u"textures/x.ico", area[2], area[3], 
            fullscreen, CREATE.HARDWARE)
            
        if not fullscreen:
            d3d.setWindow(*area)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I was unable to find anything like “CREATE.HARDWARE” in the DirectX documentation and help materials. Also, I found the following sort of code as implementations of the d3d.CreateDevice( ) syntax and it looks entirely different:
xxxxxxxxxxxxxxxxxxxxxx
D3D.CreateDevice(D3DADAPTER_DEFAULT, D3DDEVTYPE_HAL, hWnd,
    D3DCREATE_SOFTWARE_VERTEXPROCESSING,@d3dpp, D3DDevice)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Would someone advise if the problem lies in the “CREATE.HARDWARE” command, the d3d.CreateDevice( ) syntax in d3dx, or possible somewhere else? 

Thanks

Bill

Next (0.7) release will probably be available within next week. Altough I
said previously that it might be released as a .zip package this is now
unlikely. I would probably have to create installer for people who just want
the latest version anyway. 

Something that is alredy done:
-2 new samples (Winter and NumPy/array)
-Several updated samples
-Bug fixes, feature additions and minor optimizations.

More detailed log will be in the readme.txt as usual.

Maybe included if time permits:
-A small game.

Not done, altough I should have:
-Tk sample is not working.
-No tutorials (I will probably add these in the website when I have finished
them).

The size of the installer will grow if all features here are included but it
should be still reasonable (in comparison DirectX SDK is 500 MBs, so there
is still some room to grow...).

Feature requests and bug reports are welcome as always. If you are fast they
might still make it for the release.

--
Heikki Salo

Version 0.6 is available for downloading. I am especially interested
to know how the new DirectPython works with different operating
systems. Older versions had problems with Windows 98 and ME. All other
feedback is appreciated, too.

Downloads:
http://sourceforge.net/project/showfiles.php?group_id=158815

I will hopefully publish a new (0.6) release during the next week. It does
not have many new features as I have mostly focused in making the old ones
work better. However some new stuff has been added.

As I promised, this release has much better support for comtypes. I will
create a separate package for it as it has very little to do with
DirectPython. It is basically C++ programming in Python. The Frame-class
(rewritten for COM) is included as a starting point along with some
examples.

If you have any feature requests or bug reports, please report them. I can
still make some modifications for a few days before I start testing the
release.

--
Heikki Salo

> -----Original Message-----
> From: dir...@li... 
> [mailto:dir...@li...] 
> On Behalf Of Gert
> Sent: 19. elokuuta 2006 23:43
> To: dir...@li...
> Subject: [DirectPython] setMatrix not working for World objects ?
> 
> I am trying to check the possibilities of DirectPython by 
> converting the DirectX tutorials to Python.
> Can you tell me what's wrong with the following example ?
> The sprite rotates but the triangle stays in place.
> 
> I have downloaded the source-code but could not find a way to 
> compile it.
> Am I missing some makefiles or is there a trick to compile 
> the sources ?
> 
> Regards,
> Gert
> ----

It can be little tricky to built DirectPython if you are not familiar with
DirectX SDK. You need a relatively new platform SDK, the DirectX SDK and of
course Python libraries. Put everything together as a new project and built
it with Visual Studio 7.1 (you can use some other compilers too, but it
requires some tweaking). I might add some more help files to explain things,
but I think that very many people can or are interested in making their own
builts. But then again, I might be wrong.

>[Code snipped]

Vertices that are pretransformed (FVF.XYZRHW) are not affected by
transformations. You need to apply your own calculations to them before you
render them. Use FVF.XYZ-vertices if you want to use transformation
matrices. 

However, it is possible to squeese them (XYZ) through shaders to arhieve the
same results as with XYZRHW-vertices.

--
Heikki Salo