DirectX August SDK
- Thread starter Demirug
- Start date
Yes but you need Vista SP1 to get it running.
Cool thanks for the link!
PS: I finally figured out what was making DXUT dirt-slow ever since the June release: gamepad input in cameras (which is enabled for all of the default camera types), even when no gamepad is plugged in! It's so slow that even if you're not rendering anything or doing anything it will slow down the app to 200Hz max. Anyways simply changing the third parameter of all of the calls to GetInput to *false* (disable gamepad input) fixes the issue, but ideally there's a more elegant solution that allows gamepads to work without the ludicrous performance hit!
PS: I finally figured out what was making DXUT dirt-slow ever since the June release: gamepad input in cameras (which is enabled for all of the default camera types), even when no gamepad is plugged in! It's so slow that even if you're not rendering anything or doing anything it will slow down the app to 200Hz max. Anyways simply changing the third parameter of all of the calls to GetInput to *false* (disable gamepad input) fixes the issue, but ideally there's a more elegant solution that allows gamepads to work without the ludicrous performance hit!
That should hardly be surprising. Every feature addition that affects the shading language, e.g. adding a new type for cube map arrays, needs a version bump.
Mintmaster
Veteran
Unfortunately joystick ports are rather slow. They use variable resistance for the axis and I think it's measured by charging a capacitor for which the RC time constant is not particularly fast. Seems silly, but I guess 25 years ago it was a lot cheaper to have a voltage comparator than an ADC.
When I coded for the joystick way back in the day (386, Turbo Pascal), I used polling to time how long it took for the charging to happen. I think you can use interrupts too, but I don't know the details. Maybe measuring the charging time over multiple frames causes inconsistency somehow.
Huh, well I can believe that but I wouldn't expect it to be slow even when there are no (plugged in) devices! Furthermore when I used DirectInput for gamepads/joysticks I could still get >1000Hz, and that was for the whole game, not just the gamepad part! That said, maybe things have deteriorated since then, who knows.
Aha... indeed it does use XInput and that could certainly explain the slowdown. Do you happen to have a link to such a discussion? I'm only casually interested as I don't really need gamepad support right now, but it would certainly be nice for them to fix this for all of the upcoming XNA titles
I'll say it stronger: It's about time! The DirectSound API is still based on working around the limitations of ISA soundcards. It has been quite irritating to know that the current sound hardware works pretty much they way I want to program but then I have to use an API that emulates hardware from 1995.
I'm refering to how the DirectSound buffer interface artificially ties voices to samples. Back in the bad-ol-days the ISA bus was too slow to adequately stream samples in real time so you had to upload the samples to onboard sound RAM in advance. No sound cards work like that today but DSound still works as if they do. It's not hard to work around, but it's annoying and unnecessary.
XAudio2 does indeed look pretty interesting. I was lucky enough to be in a chat with the PM (I think) for XA2 back in March and was pretty excited about it after an hour of hearing about it. ISTR what I saw was a version of the GDC'07 slides boiled down to a few key diagrams and lots of talking :smile:
I'm pretty sure the GDC'07 slides are up on the DX/XNA portal for anyone who wants to see more.
Jack
I'm pretty sure the GDC'07 slides are up on the DX/XNA portal for anyone who wants to see more.
Jack
Yeah but XAudio2 can only be software accelerated (in addition it lacks the ability to support extensions like EAX). I just don't see why a develop would choose it over OpenAL. I mean what's XAudio2's mean selling point, compatibility between Vista/XP and Xbox? OpenAL already does that (with additional support for other platforms).
I just don't see why a develop would choose it over OpenAL. I mean what's XAudio2's mean selling point, compatibility between Vista/XP and Xbox? OpenAL already does that (with additional support for other platforms).
It didn't. We published the same story yesterday as well.
Silent_Buddha
Legend
That is the one feature there that has me the most excited. Now if only developers will support this. Although I'm assuming that there will be significant pressure from Nvidia for developers not to support this as I'm assuming it will by-pass their hardware AA and do the custom AA through shaders? Similar to what was done in the CoJ DX10 Demo?
The new sound system also sounds interesting. It's about time sound joined 3D in the present rather than being stuck with the limitations of the past.
Regards,
SB
From 2 months to 4 years !? Wow, Microsoft must be getting lazy.
I am not a native speaker but doesn’t “four-yearly†stand for “every three months�
Similar threads
