doh123 wrote: > > mr jingle wrote: > > > > No Idea how I should report what I've found by using a custom Library on AppDB (or Bugzilla, for the matter.) > > you shouldn't.. report it back to the people making the custom stuff, as its not something to do with Wine itself. No, by saying "custom Library" I mean the actual glide wrapper itself. In other words, there's no way to correctly specify the status of something that affects other applications, other than listing every single instance where a dissimilar behaviour appears. For example, nglide 0.98 is unable to create bilinear filtered textures, rendering every texture as nearest-point sampled(?). This only happens only on specific applications, while other games show their textures correctly. Should I file this under a specific bug for nGlide, creating an "App" profile? Or should it be considered an error of the application occurring while a specific glide wrapper is being used? The same kind of consideration could be said while using any kind of third party plugin / filter that somehow affects the whole wine/windows environment. By the way, if it weren't clear, I'm just using a stock wine build (1.5.0) running on Mac Os X Lion 10.7.3, on iMac Late 2010 (i3, AMD 5670 Video Card)