<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div><br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">One of the most useful GSOC project for gamers would be to implement DInput with XInput2.<br><br>Vitaly sent some hackish patches in Bug 6971<br><br>It could be a good start to begin to code.<br><br>A+<br><br><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;">David<br><br><br>On Tue, Mar 30, 2010 at 6:11 PM, Edward Savage <<a ymailto="mailto:epssyis@gmail.com" href="mailto:epssyis@gmail.com">epssyis@gmail.com</a>> wrote:<br>> <snip thread><br>><br>> Sorry this is a little off topic from D3D but maybe what the OP is<br>> looking for.<br>><br>> I'm not sure how easy it is but .net 3.5 sp1 is currently a blocker<br>> for several high profile games that
would otherwise work well with<br>> Wine, and many others that may work. .net needs to install correctly<br>> and function well enough so that generic .net game lunchers run and<br>> (importantly) Games for Windows Live runs and authenticates. GFWL is<br>> what many of these games rely on and it is currently blocked by .net<br>> so it's unknown how well it runs under Wine but it does install<br>> properly.<br>><br>> This maybe suited to a GSoC project and in my opinion would have the<br>> greatest positive outcome for gamers.<br>><br>> Edward<br><br>Edward seems to know what I'm after. :-) As I mentioned originally, I'm a<br>gamer and so that's where I'd like to lend my coding arm. If .net is doable,<br> I'd certainly look into that too.<br><br>> Note, I don't want to discourage you but I'm not sure if we should<br>> write any benchmark app to be bundled with Wine. When a game is slow<br>> it can be
due to a lot of factors:<br>> - quality of the display drivers, basically only Nvidia's drivers<br>> (though AMD is catching up) are well optimized<br>> - opengl extensions supported by the display driver, not all drivers<br>> support functionality like FBOs, GLSL and other stuff which is needed<br>> to run games at good speeds<br>> - behavior of the app, if unlucky the app makes calls which are<br>> inefficient to emulate (on newer cards, modern opengl extensions can<br>> remove some of the limitations and we use such extensions where we<br>> can)<br>><br>> So when you encounter a 3D performance issue, it is not necessarily a<br>> Wine issue.<br><br>I certainly agree here 100% -- however, my own previous experiences have<br>led me to conclude that there are Wine performance deficiencies *somewhere*<br>(maybe not necessarily D3D, but it seems the likely candidate). See e.g.<br>Warcraft 3 and World of Warcraft. Both of
these games have Direct3D and OpenGL<br>modes. Running each game in Wine (at least in my testing from several months<br>to a year ago) D3D was anywhere from 40-60% slower than OpenGL mode. I'd be<br>happy to test with the latest Wine, too. The point is, all things<br>being held constant,<br>calls that had to go through WineD3D were much slower. That's where<br>the spirit of<br>my proposal came from, anyways.<br><br>Now, you might say "does Wine need some sort of benchmarking?" That's debatable.<br>Maybe it could be a part of dxdiag? My goal for this proposal was to<br>create something<br>that developers could use to assess performance deficiencies, or that<br>end users (maybe)<br>could use to figure out what type of effects ought to be turned<br>off/down on their systems.<br>Essentially, answer the question "what's making my FPS drop?" Is it<br>AF, AA, specular<br>lighting, HDR?<br><br>There's been a lot of feedback so far (thanks!) So far, the
projects<br>I'd like most are roughly:<br><br>* Get .net 3.5 working<br>* Implement dxdiag<br>* DirectShow/Gstreamer<br>* The "Direct3D - Conformance / Performance / Interactive tests" given @<br> <a href="http://wiki.winehq.org/SummerOfCode#head-8d0895f237c9c3579ffe4282412bbbf2c8cd019b" target="_blank">http://wiki.winehq.org/SummerOfCode#head-8d0895f237c9c3579ffe4282412bbbf2c8cd019b</a><br><br>Again, many thanks for all the helpful feedback. I look forward to<br>(hopefully) being able<br>to work with you all in the near future. :-)<br><br>John<br><br><br></div></div>
</div><br>
</body></html>