Sat, Dec 28, 1:03 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Dec 27 9:24 pm)



Subject: Poser 7 on Vista - render button doesn't go away


MeInOhio ( ) posted Mon, 24 December 2007 at 5:33 AM · edited Sat, 28 December 2024 at 12:42 AM

I installed Poser 7 on Vista. It wasn't a breeze. It kept saying it needed elevation. My account says that I'm an administrator but it must not be the same administrator as when you right click on an exe and choosing run as administrator. That way worked, but it took a few minutes just for the install to start.

However, now that I'm installed, if I render a picture, the render button doesn't go away and I get the vista version of the hour glass. If I click on the desktop, the right side of the screen goes blank and it says that poser is no longer responding.

Anyone else having this problem?


thefixer ( ) posted Mon, 24 December 2007 at 10:19 AM

Attached Link: http://www.computerperformance.co.uk/vista/vista_performance_memory.htm

Vista has to be set up correctly in order for Poser and most other software to run properly. You need to disable the "User Account Control" for starters, that should stop the "elevation" messages! When opening Poser from a shortcut on the desktop [if that's how you have it] you need to right click and run as administrator, don't double click as you would have on XP for instance, it works differently in Vista!  I've provided a link to a very good site on how to set up Vista correctly, look at it and take some advice from it, it helped me tons when I first moved to vista!!

Injustice will be avenged.
Cofiwch Dryweryn.


MeInOhio ( ) posted Mon, 24 December 2007 at 10:54 AM

Thanks. I did find that if I wait about a minute that the button goes away. The same thing happens if I click on the little drop down at the bottom of the model area that let's you pick from 3 choices on how things display. One of them is box. It looks like poser is stuck and then after a minute it will start working again.

I will try running as administrator and look at the link you gave me. Thanks again.


thefixer ( ) posted Mon, 24 December 2007 at 10:56 AM

Issues like that could also be to do with your graphics driver, best make sure you have the latest for it!

Injustice will be avenged.
Cofiwch Dryweryn.


martial ( ) posted Mon, 24 December 2007 at 2:00 PM

I have Xp and sometime the same thing concerning render button arrive on my system.May be it is a Poser bug with memory or other set , not Vista problem

thank Thefixer for the link: : it wiil be useful for me soon :i just wait for next Penryn cpu  (the middle range) before buying  my new system and Vista 64 bits


Cage ( ) posted Tue, 25 December 2007 at 2:02 PM

Thanks for that Vista link, thefixer!

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.


Solo761 ( ) posted Tue, 25 December 2007 at 5:27 PM · edited Tue, 25 December 2007 at 5:27 PM

Don't believe everything you read on that page. Information on it seems like it's been copied from assorted sources, and poorly, at best.

Like, slow boot time is a sign that you need more memory... I have 6 GB of ram, DDR2 800 MHz, and Vista (x64) boots for 2-4 minutes. In this case this is (known) bug in Vista, if you have more than 2 GB of ram chances are that you'll have this long boot time. It seems it's an issue with Vista and motherboard BIOS/BIOS settings. In some cases after BIOS update it boots normaly. If I take 4 GB out it boots under 1 minute. Once it boots everything works normal.

Then that task manager part, amount of ram in it is not in kilobytes, it's in megabytes, and it's not 2045 for 2 GB, it's 2048 MB. Also about that ram caching feature (superfetch). When you boot up vista, hard drive will work constantly until all free memory is cached, i.e. vista will try to predict what programs you'll going to run and preload them in memory. This could be good if it's guess is right, but if it's not, it's useless. Not to mention that it could take a while to fill all memory if you have bigger amounts of ram. Luckily, you can turn Superfetch process off.

Then, in next paragraph, 72 pin simm ram was old 10 years ago EDO and FPM memory was packed in 72 pin simm modules, FPM was mostly used in 486 computers, and EDO in 486 and first pentiums. So why does he advise to "Therefore bite the bullet, order that 72-pin RAM SIMM..." is beyond me.

Next, readyboost is not a way to add more ram to your PC, it's an addon to swap file. Swap file is normaly used by windows, regardless of how much memory you have. Some "stuff" that goes in it is big, and some is small. Since swap file is on hard drive, it's seek time is much lower than ram (ms vs ns), even USB stick memory has faster latency then hard drive. Here's where readyboost comes in, if you connect USB stick to your PC and enable it for readyboost, vista will cache smaller files on this USB stick. They will also be in swap file, so if USB stick malfunctions, or is disconnected while computer is on nothing will crash, it will just revert to swap file instead of USB stick for those files. In real world, applications will start few seconds faster if it's enabled, maybe...

When I look at it again, don't believe anything you read on that page :). I don't know why they state so much useless (and wrong) stuff, only memory advice for normal vista work should be 1 GB minimum, 2 GB recommended, more if you use applications that can use more than 2 GB ram and of course 64bit version of vista. If you have 4 or more GB of ram on 32 bit vista it won't recognize more than 3.25GB of ram. That's the limitation of 32bit OS, nothing windows related.


Cage ( ) posted Tue, 25 December 2007 at 10:16 PM

Whoa.  I guess I won't bother to study that page, then.  LOL

How does one deactivate this Superfetch?  I've had this trouble with the HD grinding on and on, and your description seems to fit my problem.

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.


thefixer ( ) posted Wed, 26 December 2007 at 3:48 AM

Well actually, while there may be "some" incorrect stuff on there, it is a massive resource for Vista related issues and a lot of it, [certainly more than you are stating here] is very relevant and for me having used a lot of what is on there to tweak my Vista set up [Ultimate 64, 8 Gig RAM] it has been a big help!
I mean picking up 2045 instead of 2048!! Have you never heard of a "typo"!!
Big information sites like this will always have some errors, but they are small considering all the accurate info on there!

It's a good reference site for Vista issues and is updated regularly, maybe instead of rubbishing a decent site that sets out to help people, you offer your superior knowledge to correct any misinformation on there!!

Injustice will be avenged.
Cofiwch Dryweryn.


Solo761 ( ) posted Wed, 26 December 2007 at 9:02 AM

Yes, it probably is a typo, but "Therefore bite the bullet, order that 72-pin RAM SIMM..." is hardly a typo :). As I understood that page, it deals with how much memory is enough for Vista, and that's simple, 1GB for basic work, 2GB for advanced work (and games), more if you work with memory intensive applications (like 3D software, picture editing software...).

btw. those things I complained about are mostly basic computer knowledge, except what exactly are superfetch and readyboost. I didn't mean any of it as an insult, but that article looks like it's been written by someone who doesn't exactly understand what and why some things do what they do (like "How much RAM memory does Vista need?" paragraph, that memory limit isn't put there by vista, it's because vista he talks about is 32 bit). I'd rather trust sites like http://www.vistax64.com/tutorials/ than sites where you can't comment and discuss on tips they offer.

@Cage**

**Right click on "Computer" icon (either from desktop or start menu) and choose "Manage". When it opens expand "Service and Applications" and click on "Services". In the (pretty big) list find "Superfetch", luckily they're in alphabetic order. Right click on it and select "Properties". Under "Startup type" choose "Disabled" and click on "Apply", now just click on "Stop" button and it Vista will stop this process immediately. This stop thing is not 100% necessary, when you restart your computer next time it will be stopped.

With this caching is not disabled, windows will still cache memory, but it will be more discreet.

If you wan't to see what else can be turned off check this page

http://www.blackviper.com/WinVista/servicecfg.htm


Kendra ( ) posted Wed, 26 December 2007 at 12:40 PM

Suggestions I've tried are:
Move Poser out of the "Program Files" file.
Change the compatibility on both the poser.exe and the ffrender.exe and in that same panel choose “disable visual themes” and “disable desktop composition”.    

Since doing that my poser works a bit better than it did before and my problems were mainly the render freezing up at the end.  I still have a hard time with it freezing when I try to delete anything and I often have better results if I render from the "render settings" panel.  

Good luck, I hate Vista.

...... Kendra


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.