First off, let me start by saying great job to the Wine devs and everyone who makes this project what it is. You guys continue to blow me away with some of this stuff.
That said, I'm having a bit of trouble with Wine (1.3.29) and was hoping maybe someone more knowledgeable than I could help. I'm working on trying to get a piece of in-house software (read: not in AppDB, never will be) that was written/compiled under Windows running in CentOS 5.6 (x86_64) and have been having one hell of a time at it. I can get the program to run, its networking-related processes all work fine, and the thing gets me to the main "map" interface- this is where my problem is.
Before I continue, its likely prudent to mention the app utilizes the Qt framework, as well as the Envitia MapLink Pro 6.0 API for rendering maps (all 2D). I don't know if anyone has experience with these under Wine, but I figure it bears mentioning since no one can really try the program out on their own...
My issue is that whenever there is map interaction- mainly zooming in/out or panning- there is a seriously noticeable slowdown, sometimes partnered with Xorg -> %100 CPU. If I disable some of the map's detail layers (geospatial data and depth markings- i.e. lots and lots of lines being drawn) then things tend to pick up a bit; obviously we need those layers though so thats hardly a fix. I had thought the MapLink parts used DirectDraw for rendering, but nearest I can tell that may or may not be the case.
Any chance anyone has some advice? Everything runs, its just the "stuttering" of zooming and panning is no good. I've made sure all the usual stuff is in order- direct rendering, various registry tweak combinations, upgrade Nvidia driver, etc- but nothing tends to make a big change. This strikes me as especially strange because even *if* the CPU was handling the drawing, I feel like the slowdown should be nonexistent because the testing rig I'm using is a behemoth- 32GB RAM, Xeon 2.50GHz and an Nvidia Quadro FX 1700.
I know this is not much to go on, but any bits of advice are hugely appreciated. I'm this close and its driving me nuts.
Troubleshooting 2D Graphics / Speed Issues
Re: Troubleshooting 2D Graphics / Speed Issues
Sounds like DIB problem. Or rather Wine's lack of proper DIB support. It's the area under heavy development ATM. So you might have to wait for few Wine releases.gbw788 wrote:My issue is that whenever there is map interaction- mainly zooming in/out or panning- there is a seriously noticeable slowdown, sometimes partnered with Xorg -> %100 CPU.
Also to be sure it's not a recent regression, try stable Wine version (wine-1.2.3).
Thanks for your response! Unfortunately, thats what I was kinda worried to hear; my hope was I overlooked something. For what its worth though, I have noticed a steady improvement in the speed issues in every consecutive release, so the progress being made is definitely promising.
I believe I've tried 1.2.3 (its getting hard to remember what versions I have and haven't tried) but I'll give if another go, if for no other reason than to compare it vs the most recent.
Out of curiosity, is there a specific code branch that maintains a more complete DIB engine (even if its buggy)? I have an idea I'm opening a whole new can of worms venturing down that path, but at this stage I'm kinda shooting from the hip either way...
I believe I've tried 1.2.3 (its getting hard to remember what versions I have and haven't tried) but I'll give if another go, if for no other reason than to compare it vs the most recent.
Out of curiosity, is there a specific code branch that maintains a more complete DIB engine (even if its buggy)? I have an idea I'm opening a whole new can of worms venturing down that path, but at this stage I'm kinda shooting from the hip either way...
I don't think so. The guys working on the DIB engine are probably checking
stuff into trunk as quickly as they can get it written and debugged.
Do any of the demos at http://www.envitia.com/products/product ... id=11,82,0
suffer from similar problems?
stuff into trunk as quickly as they can get it written and debugged.
Do any of the demos at http://www.envitia.com/products/product ... id=11,82,0
suffer from similar problems?
I suppose thats just as well; thats likely a path that would have driven me crazier at this point... 
Insofar as the demos- I believe I've tried the C2 in a somewhat different form (had to compile it from scratch, so presumably its at least slightly different than Envitia's precompiled binaries) and I haven't touched the 3D, as 3D mapping and the fancy OpenGL/DirectX features aren't part of whats being used and thus irrelevant. For the C2, there isn't really any slowdown. I have an idea the core source of the issue is the very large amount of DBDBV data shown in its respective layer; its also far more than the C2 demo displays. If the map is kept zoomed fairly closely in things run fine, but as one zooms out and progressively more and more of the DBDBV is drawn onscreen, things slow down accordingly. I'm assuming this is because of all the lines being drawn- even if zoomed so far out that the finer details are pointless.
This would all make sense to me if not for the Xorg oddity as well. Though it normally maintains an appreciable amount of CPU use, I notice if I zoom all the way out or in and try to go farther, CPU use takes off like a rocket; sometimes locking up Wine altogether.
As for v1.2.3- sadly, no dice. I'm beginning to wonder if I would have better luck under CentOS 6, since 5.6 has somewhat dated versions of GCC, kernel, and all the tertiary/optional packages for compilation (if it has them at all). As another thought- and I realize I may be really stretching here- are there any known issues with VMWare Workstation being installed and/or running on the same machine? I know it installs a bunch of kernel-related stuff and I'm wondering if there is something video related that could impact performance?
Insofar as the demos- I believe I've tried the C2 in a somewhat different form (had to compile it from scratch, so presumably its at least slightly different than Envitia's precompiled binaries) and I haven't touched the 3D, as 3D mapping and the fancy OpenGL/DirectX features aren't part of whats being used and thus irrelevant. For the C2, there isn't really any slowdown. I have an idea the core source of the issue is the very large amount of DBDBV data shown in its respective layer; its also far more than the C2 demo displays. If the map is kept zoomed fairly closely in things run fine, but as one zooms out and progressively more and more of the DBDBV is drawn onscreen, things slow down accordingly. I'm assuming this is because of all the lines being drawn- even if zoomed so far out that the finer details are pointless.
This would all make sense to me if not for the Xorg oddity as well. Though it normally maintains an appreciable amount of CPU use, I notice if I zoom all the way out or in and try to go farther, CPU use takes off like a rocket; sometimes locking up Wine altogether.
As for v1.2.3- sadly, no dice. I'm beginning to wonder if I would have better luck under CentOS 6, since 5.6 has somewhat dated versions of GCC, kernel, and all the tertiary/optional packages for compilation (if it has them at all). As another thought- and I realize I may be really stretching here- are there any known issues with VMWare Workstation being installed and/or running on the same machine? I know it installs a bunch of kernel-related stuff and I'm wondering if there is something video related that could impact performance?
