25 There is still a weird problem with selecting lights. If you have a light selected and click on something else (high likelihood if you choose another light) that light will ping into a new position. Undo fixes it, and I expect I'll be using the multiple undo to fix the ones I didn't notice till too late. The light usually jumps as much as 30-45 degrees. It sure makes using the globe to position lights a load of fun.

1. Yes the hair still flys away in P7. If you use hair from P4, or P6 runtime and add it to any figure and repose that figure the hair will fly away. Even if it is parented to head.

skee.

Quote - 26. Yes the hair still flys away in P7. If you use hair from P4, or P6 runtime and add it to any figure and repose that figure the hair will fly away. Even if it is parented to head.

skee.

Sometimes that's caused by a pose that has hair positioning data in it. I don't think this is a poser bug but just unwanted pose data in a pose file.

1. While the Select option is a welcome solution to the problem with click selecting (position the cursor over an object stack and right click for a nice surprise), there is something haywire in the click selector generally. I routinely get sudden attacks of "No Actor" "No Object" at the top of the doc window. Once it happens, I can't click on anything to get going again. I have to pull down the Actor menu and select one, even there's only one to select.
2. Sydney's Point At for the eyeballs is totally hosed. I tried pointing at the camera, and one eye crosses (it's random which one, as near as I can tell), even if the camera is 60 feet away. I tried pointing at a ball. Same effect. I tried having Judy and Kate 2 "look" at the camera and the ball. No problem. I looked in the Joint Editor to compare the eyes and everything looks kosher -- the only differences are what you'd expect for bilateral symmetry. Maybe in Setup.
3. In complex scenes, it's routine for the Camera to suddenly decide its own parameters. The one where I caught it, it had dollied out a few hundred feet and set its focal length to 955 so I wouldn't notice. Neither of which I asked for. I come back from a render and my scene is suddenly 50% or so closer (in other words, the time I spent framing it is history). While I'm working with a Hand camera, the focal length changes and the distance changes, and suddenly I'm apparently the same distance away, except I have a fisheye view.
4. I was afraid eF had bought out Blacksmith a few weeks after I purchased it, when I read about the Morph Shaper. No, they've just engineered a truly unworkable imitation. I spent a half hour trying to make the tool, the instructions, and the Fisher Price fold on a sitting Miki resolve into something, anything, that made any sense. I don't think the Blacksmith3D folks have anything to worry about. Buy B3D and enjoy.
5. When I go to the Material Room, a 1/5 screen artifact blocks my view of the palette until I click on the palette.
6. If I go to the Face room with a figure selected but NOT the head, using the Face Camera, then I get told I'm using a non-supported figure (Sydney in this case) and when I go back to the Pose room, the "Face" camera is staring at her feet from ground level.
7. Chaotic lack of synchonization between red outline, doc window object selection, and parameters palette object selection. For example, I just clicked on Kate 2's neck. I have no red outline, the doc window says I selected her neck, and the parameters palette says I selected her right shoulder. And there's no telling which is correct. I click again, in the Face Camera, on her NECK, and I select the GROUND, which isn't even visible in the viewport, much less in clicking range.
8. Apply Kate [stranded] hair to her head in the Hair room. Click on the Hair length dial without moving it (or the hair length field without changing it), and the guide hair springs up as if electrified. The only way to get it back where it was is to Undo. The same thing happens if you click any Growth Control, but not if you click any Dynamics Controls. I emphasize, this happens without you actually "changing" anything except the focus, and it can't be fixed, only undone. I'm running a render to determine if the actual hair render is hosed. If you are happy with the new P7 rendering speed, stay away from the Hair room and keep your joy.
9. Kate Casual is actually a conglomerate of a half-dozen figures, such as Kate Left Shoe. If you run a render of her face (neck, head, and hair, to find out if the electric hair is really sticking straight up), P7 loads the texture for her shoes ... and is nice enough to let me know it's busy doing that. In case you wondered why Poser renders are glacially eternal. Truth be said, P7 is lightning compared to P<7, but if it didn't load shoe textures to do face pictures, maybe it could actually compete with other programs.
   That's enough for now. I'm getting depressed.
   M

PS: Finally the render is complete. Based on the messages while building the render, it's obvious that it built everything in the scene, visible or not. And the answer is yes, Kate's 'do is totally hosed. Without changing anything; just for touching a Guide Control. Sheesh. I guess nobody noticed that before they went gold....

Oh my heck. Is "sheesh" a bad word? I mean, you KNOW what it stands for!

1. Parenting is randomly hosed. I ran into a bunch of problems while arming some ladies yesterday. Here's the latest: Load Kate 2 P7 Conforming hair. It "pops" as if going where it belongs. Now for some such hair (Syd's, for example) the next step is to Conform to the person. You can't do that for Kate 2. The apparently same kind of hair is not a figure but a prop. Except that you can't parent it to the head either. So as soon as Kate moves, the hair is no longer in position.
2. And a notable bug, in the sense of brain-dead feature, remains. You still must delete stranded hair one group at a time. If there's another way, I've never found it. The intuitive thing is to delete the skullcap-- er follicle set. But that definitely is a mistake. I know! How about saving everything in the scene except the hair, and then opening a new scene and then.... Sigh
   M

Noticed problem #5 too : "delete" not working. Instead the library window moves up one level, for example from "characters" to "libraries".
A nag rather than a bug is the fact that unlike P6, P7 doesn't remember your image saving settings :
- the format, always returns to png.

• the compression rate (for jpg), always set to 75. 

A final nag is the recurring pop-up window (on which you have to click) regarding the lights when applying SSS in the material room : you can't change anything, so why the need for a message. If I'm not mistaken this nag appeared with the last service release of P6.

I hope someone from E-Frontier is going to read all this but I rather think that if they see this they will go " Wow, 2 pages (until now), let's keep that for Poser 8 ! "

"and when I go back to the Pose room, the "Face" camera is staring at her feet from ground level." I too have had this problem and not just from going from the face room. It also happens when going from the Materials and cloth rooms.

Random crashes to desktop also, but I think that one has already been mentioned.

1. On OS X, the preferences will not save properly. Some, like the main posing window placement and size, will work correctly. The lights and camera panels return to their default positions on startup. I normally hide the editing tools, view tools and the dots but these also return to their default positions and visibility on startup. This works correctly in P6 but not in P7. Other then this problem, I really like this new version of Poser. Being able to multi-thread the rendering process is a real improvement. For most renders, it has cut the render time in half. But if there are any lights using ambient occlusion there is only about a 20% reduction in the render time.

1. When importing an .obj file.... the model loads, but several verticies jet off into the distance like  drawn perspective lines. As you move the camera the verticies move too. I even tried exporting a figure and some props out as an .obj file then reimporting the new .obj back into P7 - I got the same problem.

To check that the .obj was not corrupt I opened in UV Mapper and 3ds max.... it was perfect. I saved the .obj while it was in UV mapper and imported it back into P7 and it opened without the above mentioned problem. Has anyone else experienced this?

I hadn't seen that with meshes I've imported so far.  I suspect it was some problem specific to that mesh.  What app originally exported it (if you know)?

...off the top of my head (from previous testing), Poser does not support line-continuation in .obj files.  This would show up in the file as a single backslash at the end of a line, meaning that there is more information about this record on the next line of the file.  These are normally only found on facet records, so it doesn't sounds like that is the problem (unless there happens to be one up in the vertex records).

Another issue could be negative values for vertex indices... if there are negative values in the facet section, this indicates a 'relative' index (count backwards, from current position), instead of an absolute index (count forwards, from start of list).  Poser 6 handled these fine, but it's possible that that broke in P7.

There could be some other 'non-standard' or uncommon formatting in the file that's causing P7 to choke on it.  UVMapper is pretty good about reading most .obj files, and it doesn't do anything wierd on export, so that's fixing whatever the issue is.

I just imported the mesh that caused this problem yesterday - opened fine, no problems.
Seems there's a new issue with every new scene :) lol

For instance, today checking the "depth of field" option crashed firefly 5 times in a row, but by unchecking it the render completed without issue....not sure this is a bug.... just another irritation. I'm gonna restart and try the same scene again to see what happens :)

thanks for the reply Spanki

I just got a reply from techsupport@e-frontier regarding my problems with the Walk Designer. In summary, the response was that Poser7 doesn't support third party figures, like Victoria3, in the Walk Designer at this time.

I tried the depth of field on the same scene after a fresh boot - FFrender.exe crashed again, no out of memory message, just the "were sorry for the inconvenience, but FFrender.exe must shut down" message. Poser 7 remains open and useable.  That got me thinking, so I opened a fresh scene and only loaded a portion of the set I used before - set up my camera and it rendered without a problem, complete with the depth of field effect.

"Life is like Poser 7, You never know what you're gonna get" 

• Forest Gump

:)lol

I cannot complete a render without the application (P7) going into a hang and then white screen hang - only way out is to cnrtl-alt-delete end task. P6 used to give a 'not responding' message but if you waited it would complete a render. P7 no way just completes the progress line and the render and then just hangs - what am I doing wrong?

Everytime I save a camera setting and call it back up from the menu.A phanthom camera  image and its shadow appears stuck on the ground in the preview mode. I can't  seem to delete it or make it invisible because I can't select it.I made invisible all cameras from the hiearchy window and it still appears It disappears when you render but I like to work and save in the preview mode and this @!#%$ camera is screwing everything up. I tried the exact same thing in P6 and there is no problem there  unless I load a camera setting that was  made in P7,

I'm on my way to EF to post this complaint.
Looks like I will going back to P6 till somebody fixes this or gives me a work around!!
RATS!!!
Sorry if this is a duplicate post but I can't seem to find the first one...Must have forgot to hit
the post button

Pruiz, I doubt if you're doing anything wrong, but your graphics card may be missing an upgrade (unfortunately, that may mean an upgrade that hasn't been written yet - I had that with Poser 6).  You say, though, that Poser completes the render and then hangs.   I used to get something similar with Poser 6.    Is this where you actually get to try to save the rendered file and then get the all-white treatment (not the entire screen, but the rendered one)?   I don't think I have seen that in Poser 6 since SR3, but I haven't done much rendering in Poser 7 yet.    According to my recollection, Poser was waiting for a response, but the window requesting the response instantly hid itself behind the main Poser window.   Giving the request window priority in the Task Manager used to fix the problem - I think.   If the render has completed, in Poser 6 or 7, the output should be buffered.   Even if you lose Poser, you should be able to recover the render from the list of remembered renders.

Morgano - I just upgraded my EVGA 8800 graphics card and (cross fingers) it seems to at least let me render with default draft settings - but I think the problem may lie in changing the dpi setings from the default 72?

I am going to try higher res settings. Wish me luck.

1. I hope I'm just having a brain cramp on this one. IBLs are directional. I dunno if they didn't used to be, or the just were SUPPOSED to be non-directional, but in P7 the position of the light source changes the way the "global" lighting is applied. After discovering this about IBLs I created myself, I went back to t he prepackaged ones, and this does not seem to be true of them, only the ones we create.

I was working with a Key spot, a Fill spot, and an Infinite, plus an IBL. With everything off except the IBL, and the IBL at -90x, 0,0, the model was illuminated from above. With the IBL at 0,0,0, she's illuminated from the front. It's possible that the problem is, it's not really turning off the Infinite light, but I'm running the Render now with all lights deleted except the IBL....  With them deleted, it doesn't happen.

It's possible that the problem is really the chaotic selection effects. At one point, I switched from Properties to Parameters and modified the XYZ coords, then switched back to Properties and discovered that it had switched from Light 2 to Light 3 without my telling it to. I had modified the wrong light.

1. Because it's so awful, I'll say it again: The selectors are utterly chaotic. A few minutes ago, I had Syd's rToe on the Object menu and red outlined, but the selection on the Parameter Palette was her Left Foot, and the controls visible for the "Left Foot" were for a Light. I had to restart to get rid of the Light Controls.

Quote - 40. I hope I'm just having a brain cramp on this one. IBLs are directional. I dunno if they didn't used to be, or the just were SUPPOSED to be non-directional, but in P7 the position of the light source changes the way the "global" lighting is applied. After discovering this about IBLs I created myself, I went back to t he prepackaged ones, and this does not seem to be true of them, only the ones we create.

I was working with a Key spot, a Fill spot, and an Infinite, plus an IBL. With everything off except the IBL, and the IBL at -90x, 0,0, the model was illuminated from above. With the IBL at 0,0,0, she's illuminated from the front. It's possible that the problem is, it's not really turning off the Infinite light, but I'm running the Render now with all lights deleted except the IBL....  With them deleted, it doesn't happen.

The IBL lights act like an Infinite light in preview.
If you turn on shadows for them, then the rotation settings determine the direction, just like an Infinite light.
This behaviour is the same as it was in P6.

More experimenting with IBL, and the problem, like so many, apparently is random. I deleted all lights, reloaded my lighting set with an IBL, and this time the IBL is not directional.

It would be convenient to think I imagined all this. I spent a half hour confirming it, and now I've gone through the exact same steps to replicate the problem, and it isn't happening. This may be the most unstable boxed software I've ever purchased.

M

Quote -
If you turn on shadows for them, then the rotation settings determine the direction, just like an Infinite light.
This behaviour is the same as it was in P6.

I don't have time to check, but this may be the cause. I can't think why I would have turned shadows on for an IBL. And frankly, since you can't use Depth Map shadows with point lights (the option is greyed out), it seems to me that you should not be able to "use" shadows at  all with IBLs since a global light casting a shadow is a paradox.

M

Regarding 34: Stranded Hair--
The figure shows Syd in the Hair Room with newly appolied stranded hair. On the left, as it appears when it is loaded from the Library. On the right, as it looks after you touch any Growth Control. The change is "real," which is to say, it renders that way. Apparently this happens with all dynamic hair. So, if you create a 'do, store it, and then reload it one day, doesn't "touching" it ruin it too?

M

I'm having issues with the preview window locking up and not being able to see any additional changes being presented on screen.  The only way to see the new changes is to save the file and reopen it.  This happens with all figures and in both OpenGL and Scree3D.

Not really a bug... in past versions you could copy and paste to and from the animation pallette to a text editor or spreadsheet.   This does not appear to work in Poser 7 last I tried (someone correct me if they find out differently).  I mention it here because it was a really nice time saving trick for grabbing (and saving) scene settings (FBM included) and such.    :O)

It's not just morphing...even moving an object doesn't show up until the file is re-opened.

I don't have Poser 7, but I read up on fixs a LOT and found this at planit3d.com : http://www.e-frontier.com/article/articleview/1761/1/861/

It's an important stability fix on a WIDE variety of problems in Poser 7 I thought you folks might ba able to utilize.  The original poster was scanmead, and the thanks are do to his having a problem of not being able to open the Material Room until the actions in the E-Frontiers page were implemented.

Hope this helps someone out.

Remember Preference FILES not FOLDERS to be deleted in Documents.

42 (?) If you have a document open, and you create a series of runtimes it will spontaneously close the document after a few runtimes. This appears to be sporadic. If you then continue adding runtimes after the document is closed, from time to time it will "hiccup" (i.e. it appears to hang for 30 seconds to 1 minute) after the addition of a few more runtimes. Again sporadic. Not really a showstopper, unless you have spent ages working on a document.

when usin the symmetry menu...the clothes dont always follow when ya mirror a pose

Had this happen to me and have seen some others mentioned elsewhere.   So I will add it to the list.

Saving a pz3 (or pzz) with Exteternal Binary Morph Targets turned on can lead to the pbm file becoming corrupted which will cause Poser 7 to crash and close when you attempt to (re)open the pz3.  If you delete (or move) the associated pbm file, Poser 7 will prompt it can not locate the pbm and ask to locate it.   Telling it no will allow the pz3 file to open (allowing you to salvage something of your work) but without any of the morphs (as these are stored in the corrupted pbm file).  

The Save File option (found in General Preference Tab>MiSC) External Binary Morph Targets is set on by default.   You may want to consider unchecking this box (turning it off) until this issue is addressed. 

I am not aware if also occurs with items saved to the library using pbm.  I have only experienced it (and read about it) in regard to pz3 (pzz) files. 

Okay! Now all my characters that have magnets have turned all wobly!! O_O P7 replaces magnets with waves!  Models that are morphed with magnets no longer work. This is really annoying. They worked just fine 20 minutes a go. O_O I got a whole lotta wobly looking characters now. Teriffic.

Peelo, I have not experienced this problem yet, but on other issuses I've had with P7...
a machine restart helped resolve most of the problems I was having.

good luck :)

Quote - Had this happen to me and have seen some others mentioned elsewhere.   So I will add it to the list.

Saving a pz3 (or pzz) with Exteternal Binary Morph Targets turned on can lead to the pbm file becoming corrupted which will cause Poser 7 to crash and close when you attempt to (re)open the pz3.  If you delete (or move) the associated pbm file, Poser 7 will prompt it can not locate the pbm and ask to locate it.   Telling it no will allow the pz3 file to open (allowing you to salvage something of your work) but without any of the morphs (as these are stored in the corrupted pbm file).  

The Save File option (found in General Preference Tab>MiSC) External Binary Morph Targets is set on by default.   You may want to consider unchecking this box (turning it off) until this issue is addressed. 

I am not aware if also occurs with items saved to the library using pbm.  I have only experienced it (and read about it) in regard to pz3 (pzz) files. 

Small nit: it's PMD file (not pbm)

From my explorations of this fun new idiocy, it appears that the PMD format is a work in progress.  There seems to be incomplete thought on how the format should properly handle multiple props and/or figures stored in the PMD so as to avoid problems.  And my justification is obvious - the numerous problems people are having with them!

The fact that they recently added PMD references to scene files (which weren't there previously - possibly before SR2 for P6), shows that the efficacy of the format is unstable enough that they decided it best to have a backup plan - if the Poser PZ3 PMD fails or doesn't exist, at least they might get to an original PMD for each figure/prop that uses them.

Personally, I haven't experienced any problems with PMDs enabled, but the situation seems to be that the format isn't as bullet proof as they pretend it to be.

Quote - Peelo, I have not experienced this problem yet, but on other issuses I've had with P7...
a machine restart helped resolve most of the problems I was having.

good luck :)

Thanks blbarrett. I did reboot and it actually didn't help, but I did learn that I had this one file that works just fine in P5, that was the cause of all problems. After I opened that file in P7 , it changed all magnets into waves untill I actually closed the program. Then opening another file with magnets worked just fine. Somehow if I load the "infected" file first, it makes P7 turn all the magnets into waves and I can't understand why. Even if I press "new document" and load a new "uninfected" file with magnets, they turn into waves. Curious. But like I said, problem solved...Kinda...No more wobly, melting poser figures. So thats good. :D

I have a bug that's just popped up in the last week.  It's happened twice so far.  I'll load a saved figure and the eyebrows, eyelashes, and hair are solid.  When I go into the material room, I see that the transparency map has been replaced with the current  texture map.  If I try to reload the transparency map, whether from the list or by browsing, the current texture map appears again instead of the transparency map.
I also noticed that in the "advanced" section of the material room, the node connected to transparency has the correct name of the transparency map, but with the picture of the texture map.
Now if I turn the transparency map strength all the way down to 0 and then all the way up to 100, the tranparency map magically appears in its proper place.  However, although it's in its proper place, it doesn't have any effect.  It will do its job if I delete the texture map, but as soon as I load any texture map, the new texture replaces the transparency map, and I'm right back where I started.

I can not successfully import any 3DS files. About halfway through, an error message pops up. These are files that imported fine in P5 and P6.

(Mac system) I've been using Sydney .......... 3 characters developed from her I have made and saved into my figure library do not reload !! I just get the saved hair or what ever props I might have parented to that figure. Also pz3's or pzz's with sydney aran't reloading.... Poser asks me to find an .obz file from User>Library>Caches>PoserTemporary , or something like that, and the file isn't there , nothing is. The file then opens without a figure . So as far as Sydney goes I have to do a scene all in one session. I have everything in one organised P7 Runtime and Poser constantly asks me to locate obj's and textures. These 2 things are enough to spoil the faster render times and greater stability P7 seems to offer. Totally unworkable.

Thought I'd add my bugs and quibbles too, like many others I found problems with the delete key but the worst problem was that I suddenly and at first inexplicably started to get Low Memory warnings,
I did a general clean up but it still didn't clear the problem and it
wasn't until I defragged the drive I noticed a batch of files I didn't recognise
being shifted, I had to search in Hidden Folders to discover this;

poserTemp files.
C:Documents and SettingsdaveLocal SettingsTempPoser 7

7,965 objects 12.9Gb
 created between 13/12/07 (the day I installed P7) & 27/12/06
risen to 16.9Gb by 01/01/07

What are these, do I need them, why aren't they cleared automatically?

Other issues;

Hierarchy Editor, flashes horribly when any item is clicked

Animation Palette;

1. when dragging frames along the timeline the window expansion is jerky
   & sticks a couple of frames short of the end of the timeline.

2. Frame copying using edit>copy>paste is not consistent when
   sampling multiple frames,tends to only copy/paste one frame
   shortcut ctrl+c/v works fine.

Figure/Object Cloning

Really useful, but not always consistent (especially on 3rd party figures)
Programme gets very sluggish and cross-talky with more than 3 dressed figures.

Animation layers.

Again a fantastic addition, results so far  bit patchy,
but I think I need more practice before I can comment.

Visibilty.

Another great addition, on/off is fine but opacity levels seem rather unpredictable
when stretched over frames. Silhouettes rendering more smoothly than full renders,
perhaps not surprising, but who wants a mask out of sync with the master track? 
 
Python, sometimes works others not, can't seem to find a rational explanation for this, but I often use Ockham's "Jiggles" script for hair and tail movements, so I have to switch back to P6 to use this.

3Dave

the same cloth room fault that was in p6 for a while..on random  cloths the calculatin drape goes insane....i told it to drape 55 frames...i came back to the puter a while later and it was on 563 frames, the cloth hadnt moved at all

The background thing is really ticking me off.....once introduced into the scene even if you delete the background it renders without an alpha channel. In order to get it to render you have to reboot and then you can get it to do the alpha channel thing.  I do a lot of postwork, and this is a major inconvience.
Hope EF will fix this in the first patch.

On the mac... Opening almost any file saved by Poser 7 gives me XXXXXX(Filename)undo.obj (think that's the general name) not found.

That file is no where on my computer, skipping the file means what ever object that was (usually my main character!) is not there or is missing things like a body.

P7 Hair-room crashes to desktop randomly when a hair group styling sequence is in process - happened 3 times in 3 days. When venturing in the P7 troubled waters - save often and early ( actually all the time).

Attached Link: http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2678242

Quote - poserTemp files.
C:Documents and SettingsdaveLocal SettingsTempPoser 7

7,965 objects 12.9Gb

The first release of either P5 or P6 had no garbage collection. It literally filled people's HD with temp files. Apparently they've forgotten to do whatever it takes to have the files discarded, again. I found the same thing. There is also no way I know of to move the temp folder to a different drive. Having all that activity on my boot drive isn't my preference.

1. Saving poses for Magnets does NOT save scale info even if you check on both transform and morph target options.

2. ERROR MESSAGES SUCK! Sorry efrontier but this is totally unacceptable and has been this way since Poser 4. For 4 versions you STILL won't tell us which textures failed to load, why the renders failed (more specific than that aweful generic out of memory error) or a whole lot of other errors you provide no specific info on. For example, I have had rendering with raytracing just give up and produce a grey picture (background color). No message. To date the system STILL will not tell me WHICH texture did not load when I get a failed texture load. This is a bug and a careless one at that since programming wise this would be very easy to remedy. How about a log file? Maybe for each step of rendering you print out to an optional log file what the renderer is doing so we can review the log and see where it bailed. But the current error messaging is down right horrible and has been this way for 4 versions.

at least the error msgs look nicer now.. "something bad happened" is what i got in the cloth room

I also confirm the delete-bug is very annoying. Even the menu  "Object ->Delete Object" is sometimes greyed out and therefore NOT working.

I also found that the window showing the rendered image after rendering (Pressing button ) has lost its scroll bars. So you can´t see the rendered picture

Quote - > Quote - poserTemp files.

C:Documents and SettingsdaveLocal SettingsTempPoser 7

7,965 objects 12.9Gb

The first release of either P5 or P6 had no garbage collection. It literally filled people's HD with temp files. Apparently they've forgotten to do whatever it takes to have the files discarded, again. I found the same thing. There is also no way I know of to move the temp folder to a different drive. Having all that activity on my boot drive isn't my preference.

I've just looked at there and don't see a build up of files. All but three were dated today and appear to relate to this session (Poser Still running).

You can change the the location of the temp directory in the general preferences on the misc tab. The ones that can't be relocated are the render pref's and Sketch designer prefs (Unless someone knows otherwise)

Quote - I also confirm the delete-bug is very annoying. Even the menu  "Object ->Delete Object" is sometimes greyed out and therefore NOT working.

I also found that the window showing the rendered image after rendering (Pressing button ) has lost its scroll bars. So you can´t see the rendered picture

If the menu is greyed out it was either a figure you were deleting (use the figure menu) or something that can't be deleted like the ground or main camera etc. (At least it's been that way for me)

You don't need scroll bars on the "tear off" you can drag the image around . (Better than scroll bars in my opinion - to move down and across would be two clicks/drags on scrollbarrather than  one drag on the image)