The issue occurs on any of the runtimes associated in PoserPro 2010.

Any one else experiencing this?

I am running Win7 x64 Ultimate but I don't think that is pertinant to the issue

Quote - Any one else experiencing this?

Yes. Me, too, ever since the AIR update that was installed at the weekend. I also noticed people mentioning it on the DAZ forums, so it's not an isolated thing.

Same here.

Same here.

Strange thing is I am running the same version of Air and Windows 7 64 bit and have not seen the issues so there must be another factor involved.

Windows XP 64 here... not Windows 7.

Quote - Strange thing is I am running the same version of Air and Windows 7 64 bit and have not seen the issues so there must be another factor involved.

Where is your Poser Installed? C:Program files... or another location?

My PP is installed on E:Applications.. Mainly because of the UAC (USer Access Control)  limitations of having the runtime folder in a path location that are controlled by UAC permissions...

You are certain that you are on the same version?

The only way I was able to find out the version was to downlod the version available on Adobe's web site and attempt to install it... The installerd promptly told me that I already had the current version. 

AIR does not seem to have a control panel that will list the version and PP2010 does not provide the information (that I could find). Another quirk with AIR is that it attempts to auto-install upgrades at program start but the installer always fails the first time... a second start is always required to get it to properly install.

I've noticed the same strange behaviour on XP Pro 32bit.

Going to contact SM about this... maybe, they have a solution ready.

Quote - I've noticed the same strange behaviour on XP Pro 32bit.

Going to contact SM about this... maybe, they have a solution ready.

It's not an SM issue, this is down to Adobe. You can either tolerate it and wait for the next update or re-install AIR version 2.6.

I know, that it's Adobe's update creating the problem, but I leave it to the SmithMicro programmers to contact Adobe about this issue.
They may know what exactly is causing the problem and may get Adobe to do something about it :)

Adobe may have fixed the issue themselves. Last saturday Air updated 3 times on this machine. Win7 Ultimate x64. I complained to the wife that every time I turn the damn box on Flash and Java seem to want to update and every time I open Poser Air wants to do the same. I have no issues however; with my library. Poser Pro 2010 version 8.0.3.11916 which I think is up to date and Air version 2.7.1.19610

The report that Air updates only work second try is in the system at SM. However, I am doing nothing about it because I can't. Note that it is not second try that works, or more specifically it is not accurate to say first try fails, but rather every other try fails. One person reported that the alternation of success or failure to update can even be seen if you switch versions between 2010 and 2012. Let it fail one, then the other succeeds, first try. I do not know if the new problem with labels has been reported by enough people. I have no clue what Adobe did wrong, but I will bet my little finger there is nothing I can do in the code to fix it. Report problems to SM, always. They do not use this forum to manage issues. They will ignore you even if they see you talk here. You must talk to them.

I did report it to SM and got a message back from John, stating that the issue has been reported to the project team.
So we do know, they are looking into it. :)

I worded it carefully. I didn't wonder if it was reported. I wondered if it was reported by enough people to qualify who it happens to and who it does not. Notice there are people reporting it is not happening to them.

Without a differential diagnosis, Adobe will just ignore the issue. SM has to supply that differential data. Who has this OS? Who has that font? Who has this display driver? Who has that system font size setting?

By any chance, do those of you with this problem have an override on system font size, or the DPI? I just saw this in a PC Pitstop newsletter.

There is no [OK] button, monitor resolution. Not sure how it happens but more often than not I find computers with the wrong resolution set for the monitor. This can cause program windows to not display properly and hide buttons, options and scroll bars. Usually the correct resolution for your monitor will be the largest option given. Here's how to check: Open Display Settings by clicking the Start button , clicking Control Panel, clicking Appearance and Personalization, clicking Personalization, and then clicking Display Settings. You can now move the slider to the correct resolution outlined in your monitor's manual or choose the largest resoluton showing on the slider.

The second part of this issue has to do with the DPI settings. Do yourself a favor and check this right now to be sure it set to the default 100%. The link I'm including here will give you complete information on making changes but please know that using the default is what you want to do. Going to a larger setting because you are having issues reading text is not the solution. This will only prevent you from seeing OK buttons or seeing the complete message or Window. That's it.

I asked a question in the other thread about this, but no one seems to have answered.

what happens when you disconnect an affected runtime, then re-add it? is the text still affected or does it reset to proper layout?

My DPI is set to 100%

I've rolled back to 2.6, so am not really hurting over this.

I do have a question/comment...

Given the seemingly endless things that can impact Poser (Flash updates, Google Chrome, Air updates, etc.) is there anything we can do to  protect our Poser installs short of not using the computer for anything else and disabling all updates? Does anyone have a list of things that are known to impact Poser since it depends on all of this outside software now?

It seems like every time I turn around I'm fighting one of these issues.

@ All

Allow me to update on this one.

Windows7, 64 bit, ATI card, CCC 11.7.
Windows Security Essentials.

It is completely random.

I have folders with items with full names, just one letter, or just one number.
All in one folder.

Some folders are completly OK
Other folders are just numbers and letters.

You close the Library and poser.
Re-open.
Other items that had just one letter or number before will get full names displayed, and  items that where OK before, now just have a letter or number.

it does not matter if it was a standard item or something one made.
It does not matter what runtime either.
It does not matter what folder either.

It is, as far as I can tell from here : Random. That was for PP2010.
I could make a screengrab, close Poser, restart, go to the same folder and screengrab a completely different result.

Quote - My DPI is set to 100%

I've rolled back to 2.6, so am not really hurting over this.

I do have a question/comment...

Given the seemingly endless things that can impact Poser (Flash updates, Google Chrome, Air updates, etc.) is there anything we can do to  protect our Poser installs short of not using the computer for anything else and disabling all updates? Does anyone have a list of things that are known to impact Poser since it depends on all of this outside software now?

It seems like every time I turn around I'm fighting one of these issues.

Three is now seemingly endless, eh?

You listed them all. Prior to Google putting out a version of Chrome that locks some system thing up and won't let Poser have it, I would not have known to even suggest that it might be a possibility. We still don't know why Chrome has anything to do with Poser, since the part of Poser being impacted is the main part, the main dialogs written not in Flash or any Adobe tech. I don't know how to predict such interactions.

An update to your OpenGL driver, one that has a bug, can stop you dead in Poser.

Updates to Flash usually don't cause a problem, and have nothing to do with Poser if you are running Poser Pro 2010 x64.

Updates to AIR usually don't cause a problem, and have nothing to do with Poser 8.

It is not a seemingly endless list when the list has three things in it, but for any given version of Poser, it only has two things in it.

If you are so "Pro" that you cannot afford a couple days outage of Poser as your workflow-derived income will put you in the hole, then I guess you really should not take any updates unless something is broken. If it ain't broke, don't fix it.

On the other hand, if you're honest with yourself, and you're a hobbyist making this out like it's ended your life - stop that.

No, it's not the end of the world. It is a minor inconvenience.

I'd still like to guard against it if I can. And as you've said, I now have my system set to where "if it ain't broke  don't fix it." That is my answer.

I just hoped there was an easier way. Pardon me for asking.

"Pardon me for asking" has an unpleasant twang to it. If you were offended, please accept my apology. I meant no offense.

Unless I call you a dumb-ass, you can assume anything I'm saying is with a smile on my face.

I like amusing and pithy wording. Sometimes it is interpreted as insult, instead of just a funny way to say things.

No apology required. But thanks for offering it. It just sounded like I had, as seems to be my way, pissed you off again.

I'm like you. If I think you're a dumb ass, I'll call you one in those words. I obviously must have had some prickles in my original post. I apologize for those, if they were there.

I'm going to bump this post up just to inform those individuals having problems with the same issue except on the 32bit OS.  While the 64bit version displays errors with the AIR update, the 32bit OS also has similar issues.  I experienced the same errors on Windows XP, 32bit, and the only solution was to reinstall the previous version of Adobe Flash Player.  The current update appeared at the same time the AIR update became available.  For those with identical issues, go to link below for the archived Adobe Flash program.

http://kb2.adobe.com/cps/142/tn_14266.html