| Versions |
  |
|
| Author |
 Topic  |
|
rhinnard
USA
21 Posts |
 Posted - 28 févr. 2006 : 20:49:35
|
I have been watching and participating in the Beta cycle along with other users with anticipation the SE_VGA (hacked VGA) screen issues would be resolved.
As of the current release this is not the case and I make an assumption, based on the fact that no new machines have been released with VGA screens, that I may never see this resolved.
If this is one of the items on your list(s) to be addressed, however low on the list, will it eventually be resolved?
Please let me know and thanks in advance,
Bob |
|
|
Ads
|
|
|
Ris
USA
679 Posts |
Posted - 28 févr. 2006 : 21:32:13
|
It's on the list, but it's waaaay down deep on the list.
Mapopolis works great under native VGA, so we recommend that you remove the SE_VGA hack and allow Mapopolis to run in the native/default VGA environment.
My understanding is that you need the SE_VGA hack to make other third-party software run properly on your Pocket PC. We view this as the other software vendors' problems, and they should update their software for VGA like we did.
But since they probably won't, and since many users will continue to want to use older software on newer devices, requiring a hack like SE_VGA, we have plans to EVENTUALLY make this compatible, but it is stuck at a low place in the priority list because of the points mentioned above.
We have plans to address a category of enhancements we have dubbed "VGA enhancements" in the near future (the next month or two), which will include bringing parity between zoom levels on VGA and QVGA devices, and enhancing the street labels. Since you brought this to my attention, I'll see if we can work in SE_VGA hack compatibility when we address those other issues, but can't promise anything.
Best Regards,
Ris
Project Manager for Windows Mobile Platforms
Mapopolis.com Inc
C Code
C Code Run
Run Code Run!
Run Damnit Run!! |
 |
|
|
rhinnard
USA
21 Posts |
Posted - 01 mars 2006 : 06:08:24
|
Ris,
Thanks for the prompt reply and that's all I can ask is that it be considered.
We took a trip to Indiana last October and much as I preferred not to had to run Mapopolis in standard VGA mode (not SE_VGA). It of course worked very well and got me where I wanted to go with a few minor glitches which turned out to be the windshield mount and not the program. The mount has a built in speaker which quit working on a few occasions.
I have been an avid fan of this software since I discovered it, will continue to support it and would really appreciate the effort regarding the screen display.
Thanks again,
Bob
|
|
|
|
Ris
USA
679 Posts |
Posted - 02 mars 2006 : 02:40:30
|
Hi Bob,
I sort of got the impression that you're reason for wanting to use Mapopolis with SE_VGA instead of native VGA is that you prefer the look and feel of Mapopolis in a QVGA environment vs. a VGA environment. This is understandable because of the nature of our current VGA implementation, which was done expediently with just barely enough to make it work passably well. The result has been that Mapopolis on a VGA display looks "smaller" in a sense, exactly as if you were looking at it from twice as far away. Street lines are thinner, you can't zoom in as far, and it's harder to read the text, etc.
Our plan is to make Mapopolis look the same on VGA as it does on QVGA, but "crisper" instead of "smaller", which will make the text labels more readable on the map, the street lines thicker, the zoom levels the same as QVGA, and several other things we've noted about VGA vs. QVGA. Please correct me if I am wrong, but it sounds to me like this is what you really want, whether through compatibility with SE_VGA, or if it is built-in to the Mapopolis software.
Thanks for your continued support!
Best Regards,
Ris
Project Manager for Windows Mobile Platforms
Mapopolis.com Inc
C Code
C Code Run
Run Code Run!
Run Damnit Run!! |
|
|
|
AllanHvass
Denmark
396 Posts |
Posted - 02 mars 2006 : 07:17:50
|
To solve this in a more general idea, how about a slider or something to control the zoom level of the application itself? That way, people can adjust to their individual device, viewing distance and other preferences.
Not quite sure of cause, how many areas it will affect. The navigation pane and other aspects already autoadjust to the space available. Menus and other fixed text windows uses built-in fonts which should be scalable. The main issue could be the map symbols and fonts, which I believe is pre-rendered? Perhaps rendering them at e.g. 5 different resolutions would make it a smooth zooming experience.
Best regards
Allan Hvass
Using SmartPhone QTek 8020, 512MB miniSD, BlueTooth enabled Holux GM-210, Mapopolis, Parrot BT car kit |
|
|
|
Ris
USA
679 Posts |
Posted - 02 mars 2006 : 18:45:52
|
Hi Allan, that's an intriguing idea. Something along the lines of a "magnification level" which controls the size of street lines, map label fonts, and icons, independant of the "zoom level" which controls the map scale of, e.g. one inch to a mile.
Best Regards,
Ris
Project Manager for Windows Mobile Platforms
Mapopolis.com Inc
C Code
C Code Run
Run Code Run!
Run Damnit Run!! |
|
|
|
rhinnard
USA
21 Posts |
Posted - 03 mars 2006 : 02:46:13
|
Ris,
I’m not sure what you mean by preferring the look and feel of a QVGA screen vs. a VGA screen.
To clarify, what I prefer is all the icons, fonts, etc. are one forth the size of a standard QVGA display. All my programs will run this way but not all fill the screen. Those that have a tool bar with icons at the bottom of the screen behave nicely. When I run Mapopolis in the SE_VGA screen display, at first everything is fine till I tap and drag across the map display. When I do the map zooms to what appears to be about QVGA resolution and then returns after I lift off the screen. Following this action the bottom tool bar is now invisible. It also messes up the top of the screen which returns, however, it is no longer a clean display. I have found that by entering any other menu screen and then exiting will refresh the bottom tool bar but does nothing to clean up the top one.
I guess I'm one of the nuts that can actually see this stuff and really like the extra screen real estate for the programs that take advantage of it.
Thanks,
Bob
|
|
|
|
lghtwave
USA
3 Posts |
Posted - 15 mars 2006 : 08:37:28
|
quote:
Originally posted by rhinnard
I guess I'm one of the nuts that can actually see this stuff and really like the extra screen real estate for the programs that take advantage of it.
I also use SE_VGA all the time and have a same problem like rhinnard.
It is true that fonts are smaller than normal VGA mode, but it is much more convinient to use all 480x640 screen. This means 4 times more information. Once you got used to it, can't give it up.
I used my Axim x50v with SE_VGA and had no problems until I tried Mapopolis.
Many other programs fixed this display problems and works fine in hacked VGA mode in past one year.
So why not mapopolis?
The solution is simple only if we use in normal VGA mode, but there are also so many people who use their PDA with hacked VGA mode.
I'm one of the person who really want this problem can be fixed.
|
|
|
|
Ris
USA
679 Posts |
Posted - 15 mars 2006 : 22:59:51
|
Hi Lghtwave and Rhinnard, the problem you have described is related to the use of GAPI, the Game API for fast graphical performance. Mapopolis uses GAPI, and GAPI does not run correctly in the VGA environment, at least not the way we use it. Other programs that don't use the Game API for optimized video/graphics performance would not show this problem.
When mapopolis detects a VGA display, it shuts off GAPI to avoid the error, and uses a different slower method to draw the map. The Axim is a relatively new, high performance device, and the slower method of drawing the map without GAPI is not slow enough to notice the difference. On older devices, GAPI makes a big improvement and is absolutely necessary.
When you run Mapopolis under SE_VGA, Mapopolis doesn't detect that it is a high resolution display because you tricked it with SE_VGA, so it thinks it is OK/appropriate to use GAPI, which results in the problems you have described.
GAPI has caused problems on various new models in recent months, and we have a reliable backup method that we use on systems that do not have GAPI support such as WM5 or high res VGA systems where it doesn't work. So I think what we may do is change GAPI to a user option, so that you can turn it off MANUALLY, which might allow Mapopolis to run fine on an Axim under SE_VGA. I'm not sure if that's the ONLY problem, but it seems to be the main one.
Best Regards,
Ris
Project Manager for Windows Mobile Platforms
Mapopolis.com Inc
C Code
C Code Run
Run Code Run!
Run Damnit Run!! |
|
|
|
lghtwave
USA
3 Posts |
Posted - 16 mars 2006 : 05:50:25
|
Thank you Ris.
That might solve this problem.
I really do appreciate your work.
Can't wait for the next version. :D |
|
|
|
annabelle
2 Posts |
Posted - 17 mars 2006 : 18:51:55
|
quote:
Originally posted by Ris
Hi Lghtwave and Rhinnard, the problem you have described is related to the use of GAPI, the Game API for fast graphical performance. Mapopolis uses GAPI, and GAPI does not run correctly in the VGA environment, at least not the way we use it. Other programs that don't use the Game API for optimized video/graphics performance would not show this problem.
When mapopolis detects a VGA display, it shuts off GAPI to avoid the error, and uses a different slower method to draw the map. The Axim is a relatively new, high performance device, and the slower method of drawing the map without GAPI is not slow enough to notice the difference. On older devices, GAPI makes a big improvement and is absolutely necessary.
When you run Mapopolis under SE_VGA, Mapopolis doesn't detect that it is a high resolution display because you tricked it with SE_VGA, so it thinks it is OK/appropriate to use GAPI, which results in the problems you have described.
GAPI has caused problems on various new models in recent months, and we have a reliable backup method that we use on systems that do not have GAPI support such as WM5 or high res VGA systems where it doesn't work. So I think what we may do is change GAPI to a user option, so that you can turn it off MANUALLY, which might allow Mapopolis to run fine on an Axim under SE_VGA. I'm not sure if that's the ONLY problem, but it seems to be the main one.
Best Regards,
Ris
Project Manager for Windows Mobile Platforms
Mapopolis.com Inc
C Code
C Code Run
Run Code Run!
Run Damnit Run!!
I am also the one who uses SE_VGA most. It would be nice if Mapopolis could run in this model. Thanks.
Belle |
|
|
|
lamar@mapopolis.com
USA
2508 Posts |
Posted - 17 mars 2006 : 21:35:45
|
Hi, Annabelle,
Welcome to the forums.
Lamar
"I should like to spend the whole of my in life traveling abroad, if I could anywhere borrow another life to spend afterwards at home."
— William Hazlitt |
|
|
|
annabelle
2 Posts |
Posted - 18 mars 2006 : 05:42:23
|
quote:
Originally posted by lamar@mapopolis.com
Hi, Annabelle,
Welcome to the forums.
Lamar
"I should like to spend the whole of my in life traveling abroad, if I could anywhere borrow another life to spend afterwards at home."
?William Hazlitt
Thanks, Lamar. |
|
|
|
admin_0
1 Posts |
Posted - 10 mai 2006 : 17:40:42
|
I have a HP iPAQ hx4705 and also keep it in SE_VGA mode. Personally, I try to stay away for the QVGA environment. I like the smaller icons, smaller text, thinner street lines, etc. If your plans are to make 'Mapopolis look the same on VGA as it does on QVGA', count me out... I like the idea of being able to turn off the GAPI.
If all programmes on a desktop computer was designed for a 800x600 display, why buy a monitor that can display 1280x1024 or higher resolution.
BTW, I tried to switch to WM5 and used OzVGA since SE_VGA is not available on WM5. OzVGA does not offer trueVGA like SE_VGA does. Too bad Microsoft does not allow me to switch screen resolutions like it does on it's desktop versions of their software. |
|
|
|
Ris
USA
679 Posts |
Posted - 10 mai 2006 : 20:54:33
|
The fresh activity on this thread has brought my attention back to it, so I thought I'd just mention that the latest beta 4.71.03 includes the feature to disable GAPI for this purpose. There is a checkbox for this feature under General Program Settings. As far as I know, it does work successfully to make Mapopolis run without cosmetic problems in an emulated QVGA environment on a natively VGA device, so it should work with OzVGA. So far, I've only seen one report on this feature, very much in the positive saying that it solves the problem and definitely allows emulated QVGA operation of Mapopolis on a VGA device via this kind of third party software, as long as you disable GAPI. You can find the download link for the latest beta if you look in the news or beta sections of this forum, which both contain a sticky post to discuss the latest beta.
Best Regards,
Ris
Project Manager for Windows Mobile Platforms
Mapopolis.com Inc
C Code; C Code Run; Run Code Run; Run Damnit Run!! |
|
|
|
rhinnard
USA
21 Posts |
Posted - 13 mai 2006 : 07:05:12
|
Ris,
My original message in the main forum may have gone unnoticed so to make certain you and others see it copied into this reply message as follows:
Ris,
I would like to thank you and all the other fine people at Mapopolis for the continued support of our devices.
I now have the full screen VGA support by this releases GAPI option which makes me very happy to see finished.
IMHO, Mapopolis is the very best navigation software for handheld devices and I just wish you had a version that would work on my laptop.
Thanks again,
Bob
By the way, I use SE_VGA and this release works full screen without any problems so far.
Great work as usual from the team at Mapopolis!
Go to Top of Page |
|
|
|
Topic |
|
|
|
| This page was generated in 0,77 seconds. |
 |
|
- 
- 
Hacked VGA support?
Forum Locked
