March 2018 - Wine-Devel - list.winehq.org

Re: Call for WineConf presentations

by Alex Henrie

On Thu, Mar 29, 2018 at 8:35 PM Alistair Leslie-Hughes < leslie_alistair(a)hotmail.com> wrote: > I would like to hear about support for DTXn. (as long as someone > records it for me). Since the patent on this format has expired. > It's now officially part of mesa(17?), and since a large number of bugs > depend on this missing feature. How could we get implement > it quickly? When I ran into this issue in the past with Call of Duty 2, I was able to play the game (with some graphics glitches) by turning on the driconf setting "Enable S3TC texture compression even if software support is not available". This setting no longer exists in Mesa 17.3 because S3TC compression is always available. So, I believe that the DTXn bugs will just disappear when you update Mesa. I know that Wine Staging has a patchset to hack DTXn support directly into Wine. If it were up to me, I would just drop that patchset. -Alex

March 30, 2018

Re: Call for WineConf presentations

by Zebediah Figura

I would appreciate such a presentation. How much background (if any) on the general architecture of 3D graphics do you think you'd give? (so that I know how much reading up I need to do ;-) On 29/03/18 06:02, Henri Verbeet wrote: > Thanks for taking care of this. > > Before all the good slots are gone :D, would there be interest in some > kind of introductory talk about Wine Direct3D architecture? I.e., how > the various DLLs relate, what the various blocks of functionality are, > etc. I imagine such a talk might be interesting for some of the newer > contributors, but perhaps too obvious/boring for some of the others. > Thoughts? > > Henri > >

March 30, 2018

Re: [PATCH 11/11] winevulkan: Limit vkGetDeviceProcAddr() workaround to broken apps.

by Roderick Colenbrander

Signed-off-by: Roderick Colenbrander <thunderbird2k(a)gmail.com>

March 30, 2018

Re: [PATCH 10/11] winevulkan: Avoid goto in wine_vkCreateInstance().

by Roderick Colenbrander

Signed-off-by: Roderick Colenbrander <thunderbird2k(a)gmail.com>

March 30, 2018

Re: [PATCH 09/11] winevulkan: Avoid goto in wine_vkCreateDevice().

by Roderick Colenbrander

Signed-off-by: Roderick Colenbrander <thunderbird2k(a)gmail.com>

March 30, 2018

Re: [PATCH 08/11] winevulkan: Avoid goto in wine_vk_instance_load_physical_devices().

by Roderick Colenbrander

Signed-off-by: Roderick Colenbrander <thunderbird2k(a)gmail.com>

March 30, 2018

Re: [PATCH 07/11] winevulkan: Simplify wine_vk_init().

by Roderick Colenbrander

Signed-off-by: Roderick Colenbrander <thunderbird2k(a)gmail.com>

March 30, 2018

Re: Call for WineConf presentations

by Zebediah Figura

Alistair won't be able to make it to WineConf this year; however, I will, and accordingly I'd like to schedule a slot to discuss the state and future of Wine-Staging. I do imagine that this will end up being of interest to everyone, and I wouldn't be surprised if it spawns some rather lengthy discussions, so please try to schedule us on the long side ;-) We're still discussing what this talk will encompass, but if anyone has any requests for us to consider, please don't hesitate to speak. ἔρρωσο, Zeb On 28/03/18 07:32, Aric Stewart wrote: > Hello, > > As discussed during WineConf 2017, I am helping coordinate the talks and presentations this year. > > In previous years we have been very last minute and laid back in the proposal and scheduling of presentations. While this has it's advantages I have volunteered to help call for and organize presentations further in advance so speakers have some time to prepare the presentation they wish to give. > > General Guidelines: > * Please provide an estimate of how long your talk will be. We are shooting for approximate 40 minute slots with between 15-20 minutes of talk and with likely an equal amount of question and discussion time afterward. Generally shorter talks are not an issue, however longer talks will need to be discussed and will be considered based on the rest of the schedule. > > * Topics should obviously be of interest to the other attendees, i.e., the broader Wine community, but note that that doesn't imply the talk has to be about Wine itself > > * If you have a preferred time and date for your talk please indicate that to me when you submit your talk. We will try to make it work as best we can. > > Here are the rough proposed slots, They will be changed and modified as required by the addenda as it gets fleshed out. Understand that even with this shift toward a scheduled day we will not disrupt productive conversation to fit to the schedule. The schedule will warp and flow as required to facilitate the talk, not force the talks to conform to it. This does mean if you are planing to try to attend a given talk you will likely want to arrive a bit early and understand if when you arrive the schedule is either behind or ahead of plan. > > Daily Slots: > > 09:00 - 09:40 slot 1 > 09:45 - 10:25 slot 2 > 10:30 - 11:00 break > 11:00 - 11:40 slot 3 > 12:00 - 13:00 lunch break > 13:00 - 13:40 slot 4 > 13:45 - 14:25 slot 5 > 14:30 - 15:00 break > 15:00 - 15:40 slot 6 > 15:45 - 16:25 slot 7 > 16:25 - 17:00 Overflow time / small group discussion / short presentations > > > We will track proposed presentations on the WineConf Wiki: https://wiki.winehq.org/WineConf2018 > > If this more organized presentation proposal process works well, we may try to expand it to include scheduling times in the near future. But for this year getting a working itinerary and scheduling the talks during the opening of the conference is likely acceptable. However if you have a preference toward Saturday or Sunday please express that. > > If you would like to give a presentation! Please e-mail me directly! I will keep the Wiki updated with presentations and scheduling as we get it worked out. > > If you would like to see a given presentation, reach out on the mailing list, see if you can get the people qualified to give the presentation to step up and contact me! > > Likely we will have open time at the conference which we will propose presentations and fill at the time. We have never had a problem finding things we all want to talk about. > > thanks! > -aric > > >

March 30, 2018

Re: [PATCH 06/11] winevulkan: Move some autogenerated code to vulkan_private.h.

by Roderick Colenbrander

Signed-off-by: Roderick Colenbrander <thunderbird2k(a)gmail.com>

March 30, 2018

Re: [PATCH 05/11] winevulkan: Use %#x to trace enums.

by Roderick Colenbrander

Signed-off-by: Roderick Colenbrander <thunderbird2k(a)gmail.com>

March 30, 2018