Hey, Tim ... yes, been there and no the fun of a) Getting the money together, and b) "Installing everything"  (The buildinging can be fun or "fun" too, just depending on how it goes.  My last build went pretty smoothly.)

Back  to the font ... is there a style-sheet type file where I could maybe alter the font size, perhaps?

Great, thanks.  I'm actually surprised no one else had noticed and commented on it before. 

Well good luck with the new PC, and of course take your time.  Thanks again for this great program, Tim.

-Tim

Bingo!  No crashes after switching it to FS from SimConnect.  Not sure why it was set to SimConnect in the first place.  Maybe that is the default?  Anyway, glad that was it ... thanks!

Anyway, major issue solved.  Now if I could just get the mouse wheel to work.  I'll try not using FS-Simitizer next time I use FSX just to eliminate that possibility.  Another thing I might try is mapping the +/- keys to my side mouse buttons.  Not quite the same, but maybe a touch better than using the keyboard.  Depends if it will zoom to where the cursor is using that method.

-Tim

Sure thing, here you go ...

As you can see it names the destination, but not the setting I chose (in this case "distance to").  I think there simply is not enough room.

Hey, Tim:

Thanks for the quick reply.  Yeah, it literally crashed on my a few more times in the short time since I wrote that last post.  Usually it crashes when I'm not even interacting with Plan-G.  Also, it sometimes will lose sync and I have to disconnect and reconnect.  It also does not appear to like, or keep up with, time acceleration.

I did just noticed I'm using SimConnect, so that might explain a lot (with the crashes).  Not sure why I'm not using FSUIPC, as that is pretty much what I use for anything else requiring a connect to FSX.  Will switch that over and see what happens.

Back to the mouse-wheel ... yeah, this has never worked for me since V3 came out.  I don't understand why, as it works with every other program I own that can use mouse wheel input.  Only thing I can think of is, is there perhaps some incompatibility between Plan-G and FS-Simtimizer?

Thanks again,
Tim

Another issue I've always had with V3 is that no matter what I choose, the GPS refuses to display any other info than the waypoint name.  I have tried everything.  Only thing I can think of is, the default font is too large to display the name and the requested info maybe?  But why does it insist on showing the name there then?  And can this be adjusted if is the case?

Thanks for any info,
Tim

Hi:

I've diligently installed each update, and am -- unfortunately -- dis ... (WOW, Plan-G 3.1.3) just crashed as I was typing, and I hadn't even done anything but load it up, sync it to FSX, and try out this issue I'm writing about!) ... as I was saying, disappointed.

The lack of mouse wheel support makes it mostly unusable for me ... I mean it's the way I've been using maps on a computer for nearly a couple of DECADES.  It doesn't even work sporadically for me.  It also crashes a lot more than V2 ever did.  Honestly, nothing else on my system ever crashes.  I don't understand why this app crashes so much. 

Anyway ... any idea why mouse-wheel zooming does not work?  Was it finally removed since it had been buggy in the past? 

Also, is there ANY CHANCE we'll be able to dock those windows once again?  Considering the zooming in/out is based on the whole screen, rather than the visible map, they often get in the way. 

I appreciate the effort that goes into making this app, but for me it is so close to being great, but is just falling short in these areas, and they are big enough to make using it enjoyable.

Thanks,
Tim

Sincere apologies for the LONG OVERDUE response (lots of issues/reasons I won't go into here) ... but just wanted to say thanks for the replies and info.  I will try that with the mouse wheel, however I don't think it matters ... at least for me.  The zoom in/out was sporadically working (but mostly) in V2 and could have been the case mentioned (i.e. pop-up/tool-tip), but with V3 it NEVER worked.  Again, I'll give it a shot though.

Hi, I'm just going to copy/paste what I wrote in the FSE forum regarding the V3 release and the issues I observed that are causing me to have to stick with V2.  However, before doing so, I do want to stress how much I appreciate the hard work and effort Tim has put into this software, and how thankful I am to use it ... just about every day.   What I am reporting below is in hopes to make it even better ...

==========================
Tis' a shame ... what we have here is a severe case of "takes one step forward, two steps back." Possibly even three or more steps back.  I actually find more speed (which I like of course) regarding the map's scroll and update, but there are a number of problems ...

• Mouse-wheel zooming has been "fixed" ... that is, it has been eliminated.  Doesn't work at all.  This alone, forces me back to V2 ... even with its "half-working" mouse-wheel support.


• Display of airports is ... well, inconsistent at best.  I zoomed out around the MD area, and KBWI did not show up, but KNHK did.


• Map "tags" are appearing randomly and will not disappear ... and on things I did not even click on.  What is worse, they are staying on my monitor on top of things ... EVERYTHING.  Even if I slide Plan-G to another monitor.  BIZZARE.


• The new font is horrid ... not sure why that was changed.


• Unless I'm just missing it, you can no longer dock all of the info neatly on the right as with V2.  So they just float all over the place in the way of the map.  If the dock has truly been removed, I am at a loss as to why this would be a sound choice.


• Did I mention the new font is terrible?? ;0  Seriously ... is there an easy way to change that, Tim?

A number of nice new things have been added (e.g. VATSIM, RADIO, etc integration ... and of course (for some) a massive speed increase).  Unfortunately, these nice new items are greatly overshadowed -- at least for me -- by the above-mentioned problems, which mostly boil down to core-functionality.  Perhaps a .x release will address some/most of these.  (Probably need to post my observations on his site.)

Ok, there's my two (or four) cents worth ... for what it's worth.



Take care,
Tim K.
========================

Care to clarify please?