I just noticed that when I read anything about the SR1 for Poser, that I become like a kid waiting for his birthday and all of the presents that come with it.

Is it just me feeling this way?

Frederick
Poser By Design

 Any one who dropped the cash likely is...some folk are just more vocal...you're not alone.. ...

trying not to be cynical, but what is the bet that SR1 does not get released before the 30 days are up for the early adopters?

Quote - Is it just me feeling this way?

Me too! I did a 4-hour render overnight that would be lovely, were it not for the darned ugly, blotchy render artifacts.

I really hop they release this soon.

It's just you and a few others feeling that way. According to some around here, most people do not need SR1 at all, since Poser 8 is working fine. It's only a few that need SR1 and only a handful of people experience problems with P8.

I'm eagerly awaiting SR1, hopefully it will be released soon.

Well, I know others are having trouble with the library and textures not loading, but they're fine for me.

I was under the impression that IDL was problematic for almost everyone; bagginsbill has shown in other threads that there are real improvements in render quality and speed with IDL in SR1. It is really frustrating to know that the problems have been addressed but that I can't take advantage of that. I've been back to Poser7 but that's just not doing it for me anymore.

Waiting...   Waiting...  How about some ideas on what will be fixed in SR1...?

Quote - .... since Poser 8 is working fine. It's only a few that need SR1 and only a handful of people experience problems with P8.

That reminds me, I must get some ironing done this evening.
:O)

Poor you..... maybe you have something that takes a long time to render for while you're rendering ;-)

I would say I am slightly peckish for SR1 rather than hungry.

John

I´ll admit to going to SM's download sections several times a day! I can't wait for SR1!  P8 is working great for me and I almost feel it gets faster and more stable the more I use it. But I'm not doing any complex scenes as I simply can't render without IDL now. Come on SR1!!!

I can't wait for it so the damn thing finaly becomes usable (I hope) Right now I'm having to do all the set up in Pro and then import it into 8 to render it. It shouldn't be this way.

Quote - trying not to be cynical, but what is the bet that SR1 does not get released before the 30 days are up for the early adopters?

That ship has already sailed.

Quote - It's just you and a few others feeling that way. According to some around here, most people do not need SR1 at all, since Poser 8 is working fine. It's only a few that need SR1 and only a handful of people experience problems with P8.

Not one single person in this forum has ever said that.

Quote - Not one single person in this forum has ever said that.

Yeah, I think a lot of people are able to live with P8's bugs without complaining, and that's a good thing, but I think we can all agree that Poser 8 desperately needs SR1 to be fully enjoyed by it's eager users.

Hi,
yes, waiting for SR1. I have a few crashes with P8 (not as many as with the initial P7, but significantly more than with P7 current SR, and always when I have not saved a long time),
no problems with the library (except occasional crashes when refreshing the library), but the
main issue is IDL.
Especially because BB has said that IDL will change in SR1, I do not want to waste time with the old one and then restarting.
I don't think it will take too long, because it is in testing already. I prefer a stable SR1 to a quick release with more bugs left in it. 
Currently I'm working with P7 / PPro again.

Best regards,
   Michael

Quote - > Quote - Not one single person in this forum has ever said that.

Yeah, I think a lot of people are able to live with P8's bugs without complaining, and that's a good thing, but I think we can all agree that Poser 8 desperately needs SR1 to be fully enjoyed by it's eager users.

Yes everyone does agree it needs an SR and I would guess more than one as time goes on.

Not everyone who has problems will complain. Some people simply make do, and rely on others to communicate for them. As long as some are making the obvious problems known, most folks will sit back and just read. And, of course, wait for SR1 to come out.

**Vestmann:
**
If you post the download link, I bet a lot of other people will visit it with you.

LMK

Quote - **Vestmann:
**
If you post the download link, I bet a lot of other people will visit it with you.

LMK

Do you mean the link to the SM downloads section?

Here it is:
Poser Updates

Don't mind the company ;)

Yes. Thanks. Just checked. SR1 is not there.  :/

lmk

now it is.

oops, it's gone.

:lol:

 must be very very close then!!!!

I think alot of us are just in the "well, it works quite nicely now, and I can get by until SR1 comes out, but I will be happy when it is" camp. Poser 8 is one of the best releases yet, with relatively few bugs, and the new features actually work more or less as expected.

I wish..

Quote - Not everyone who has problems will complain. Some people simply make do, and rely on others to communicate for them. As long as some are making the obvious problems known, most folks will sit back and just read. And, of course, wait for SR1 to come out.

**Vestmann:
**
If you post the download link, I bet a lot of other people will visit it with you.

LMK

That's not a good attitude. At least they should communicate their problems to SM. SM will only act on a bug if it is confirmed by others. I reported a bug, which they couldn't duplicate themselves. Later others started to report the same bugs to SM and then they gathered enough information to able to act on it.If people will sit back and wait the bug resolving goes a lot slower or at worst, the bug may never be dealt with. You can't rely on others to take responsibility on your behalf.

On the other hand only 'complaining' here isn't good either. Problems and issues need to be reported directly to SM.

Quote - I think alot of us are just in the "well, it works quite nicely now, and I can get by until SR1 comes out, but I will be happy when it is" camp. Poser 8 is one of the best releases yet, with relatively few bugs, and the new features actually work more or less as expected.

Quite logic also. With every new release of Poser, less new features are added, so less can go wrong. Poser 5 compared to Poser 4 was a major thing, completely new. From there on the changes and new additions have been less and less. Compared to going from Poser 4 to Poser and going from Poser 7 to Poser 8, this newest release isn't very impressive at all. It's more like going from Poser 4 to Poser 4 Pro Pack, then going from Poser 4 to Poser 5.

Oddly enough, I find it to be quite the opposite (IMHO): I'm much more impressed going from Poser 7 to 8 than I was going from 6 to 7. I honestly think I'll just stick with the even-numbered releases from now on.

I could be wrong, but I'm guessing in SR1 they are trying to fix everything that has been reported and confirmed as a bug, and the reports keep coming. Or maybe some of the bugs are proving to be very stubborn.

One thing I fear won't be fixed (because it's a design issue rather than a bug) is the fact that the GUI elements and text are too tiny for anyone who doesn't work on a laptop. Not just the library content icons, but scrollbars, buttons, parameter text, etc. Since 3D people tend to work on large monitors, this is a fairly significant issue. I also wish there was a way to change the dark grey interface. Too gloomy.  

That (i.e. the mail beginning "Since it has been....") is an automated response.

Quote - II think this is rather rude.  Especially since there has not been any solution offered..
Below is the last response from SM

Well, the solution offered was: Wait for the Service Release...

With no idea as to when that will be.  I still think that SM could do better..!
Thanks anyway Dizzi..

Quote - With no idea as to when that will be.  I still think that SM could do better..!
Thanks anyway Dizzi..

47 days and counting. The natives are getting restless :bored:

Everyday that goes by with no SR1, the more and more in my mind it is becoming obvious P8 was rushed out the door for the sole purpose of a SM cash injection from the early adopters.

do you suppose SR1 will fix the "not enough memory to load texture" error I'm getting all the time??

runtimes load correctly for me and renders are fine. But if i load more than one figure in the scene I get the  memory error - it's very annoying.

Quote - do you suppose SR1 will fix the "not enough memory to load texture" error I'm getting all the time??

runtimes load correctly for me and renders are fine. But if i load more than one figure in the scene I get the  memory error - it's very annoying.

Please, nobody jump down my throat for what I'm about to say. I'm not making any judgements or jumping to conclusions. You can draw your own.

Here's the thing. I looked in the bug database. It looks like (looks like, mind you, don't kill the messenger) everybody with this problem assumed somebody else reported it. Only two people reported this problem. One of them found he had done something strange and rescinded his bug report.

The other was semidieu, who did not experience the problem himself. Rather, he saw all the posts at RDNA and posted a bug on behalf of all the others. Since he never saw a problem loading textures (nor have I), it isn't at all clear if the problem was fixed. Certainly some related errors were found, and SM speculates that the problem is resolved.  Semidieu cannot confirm it because he never saw the problem. Nor did any of the other dozens of beta testers, many of whom, amazingly, spend every waking moment testing Poser 8. (Some of these heroes who work with Poser 16 hours a day talk constantly with SM engineers, and are listed on the credits dialog of Poser 8.)

So, as far as I can tell, (again, don't bite my head off) SM do not know this to be a problem. Meaning, nobody doing Beta testing has this problem. There are clearly other users who have this problem, and they have written about it in public forums. (fora?) I'm not certain that nobody told SM, but usually when ratscloset gets a bunch of customer problem reports, he makes a bug report about it. I cannot find any such bug report.

If you did not report this problem and you have this problem, (shouting now on purpose) NOTIFY SM IMMEDIATELY. If you did already report it, thank you, and go report it again. Ask them to let you have a pre-release copy of the SR1 updater, so you can confirm that it fixes it for you. They may not do that, but right now, it's a total guess as to whether it is fixed or not, and SR1 is almost out the door!

I don't want trouble, people. Please do not beat me up. I'm trying to be as straightforward as possible, and I'm not making the assumption you're all lazy and stupid. I'm just telling you what I see. Facts only - no judgement.

 Ted,
Thank you for the info.  I had reported a few issues with the initial P8 release.  John and I worked on them and I encouraged others with similar difficulties to report them as well (until I left on vacation.)  It's great to hear that SR1 is very close to release.  Thank you, the development team, beta testers and the support/sales teams for all the help... even when I've been frustrated. :)
Lee

I just installed Poser 8 and applied the small fix file, loaded my runtimes in the runtimes pane - btw, great job on this, runtimes work much better now. Then off to test by loading koji1 and  the ronin texture. all goes well and renders fine. Then i added a second figure - expressnimg's HeBot.

tried other figures as well - David with  standard maps, M3 with DAZ's high res maps, M4 with standard maps. All had the same error.

The only textures that loaded fine were from content that was installed within the Poser 8 directory runtime. All external runtimes chuck up that error.
**

Quote - I do not really know where to report the issue I'm having since CP no longer have a forum.

goto

http://support.smithmicro.com

click the "start a new incident" tab and fill in the form.

I also get that error when applying a MAT pose from an external runtime, same routine with the same files in Poser Pro works as expected.

thank you Tyger_purr! :D

ok bug reported so i don't get shouted at... :blushing: :blink:

SophiD:

Does Poser 8 load the figure but without its textures? If it loads the figures, can you apply the textures in the Advanced Material Room (buy navagating to the texture yourself)?

lmk

lkendall, yes, that's what's happening. However, when i finish applying the textures manually and click render, the same error pops up, eventhough the textures are entered correctly.

Thank you Bagginsbill and Tyger_purr.

I just reported my memory leak problem to Smith Micro. Even if I load a blank scene and do nothing, memory consumption of the Poser.exe process increases by 30KB/sec. I usually leaave my PC alone during rendering (watching TV). So, when you get back after 30min or so and move the mouse, the "out of memory" error appears, because Poser allocated a lot of memory even if it's in idle mode after rendering.

With my previous Poser version, memory consumption stays constant when I do nothing (as expected).

EDIT: Just to give you some idea. During the time it took to report the problem and write this forum post, Poser memory consumption increased from 17MB to 73MB. When I minimize Poser, memory drops again to 17MB and starts increasing slowly but steady...

One more question: The problem with Poser crashing while trying to refresh the library has been reported already by someone, right? And the 1px artifacts at the border of a render.

Been gone for a week, and so I've missed a bunch of conversations. But I will say here that I'm in serious need of that update to speed up IDL rendering on my poor, over-worked Toshiba. I like what I see BB!

SophiD:

This problem seems to occure for several reasons. I believe in most cases, the material nodes get loaded, but without the textures.

In the Advanced Material Room, click on the name of a texture, and in the dialogue box, click on the texture name with the down arrow on its left. A menu of pathway names to textures should open up. Scroll down to the pathway with a blue check mark beside it. Check to see if any of the directory names in the pathway are corrupted. Generally the first letter of the directory name is missing.

In my case this happens when the directory before the "...runtime..." directory contains a number (except at the end of the directory name). A directory name such as "...Poser7..." is okay to use, but not "...V4Cloths...". I have been able to manually load the textures, and Poser could then find them and render, so, your problem is a little different than mine.

lmk

Quote - Here's the thing. I looked in the bug database. It looks like (looks like, mind you, don't kill the messenger) everybody with this problem assumed somebody else reported it. Only two people reported this problem. One of them found he had done something strange and rescinded his bug report.

The other was semidieu, who did not experience the problem himself

BB, something is wrong then. I've reported it to SM also and after John dealt with it initially (but we could not solve it) I was told the following (Incident: 090813-000107):

Quote - I have reported this issue to the Project Team. I could not duplicate the issue, but wanted them to be aware of your report.

Here's another quote from the tech support thread (Incident: 090813-000107), a bit earlier in the thread:

Quote - The Texture issue could be due to a known Bug. Let me know if the file in question has a Capitalized Extension for the Textures used.

Not sure what is going on in the last Scene, other than Poser may be looking for a Texture, this could be related to the above.

That wasn't the issue at all and my issues were reported to the project team. I filed the report, I did not rescinded my bug report at all and the report was sent on to project team. The Tech Support CLOSED the case, but a number of the issues weren't resolved at all.

I reported the issue for sure (and I actually know of at least 4 others who have done so, one of them being Semidieu), there should be at least 5 reports.

I'm not sure if I do trust this anymore..... I reported the same issue when using Poser 7 Pro (yes, it's there also, but not as bad as it is in P8, but still there.) and I wasn't the only one back then. I was told back then by Tech Support that the issue would be dealt with. Yet, they never dealt with it at all and now P8 report are missing as well? They know it's a bug, they've confirmed that twice already, so they should deal with it. I'm getting the feeling that they may not be able to deal with it at all, since P7, P7 Pro and P8 all have the same issue. Perhaps they rather ignore it? I could be wrong of course......

Fact is.... I reported it (along with other issues), bug confirmed, yet the reports go missing, case get's closed and no one knows if it's dealt with or not?

I'm not going to re-file anything, I've spent hours with tech support, doing this, doing that, trying this, trying that and I'm not going to go through all of that again. Tech Support closes open issues more often I've noticed, without the issue being resolved. You get a final reply like 'we're looking into it' or 'we've forwarded your report' and then you never hear back again and the issue stays open. It happened to me 4 times now and none if the issues was ever resolved. I re-filed an issue that wasn't resolved once, to no avail. I'm not going to re-file this whole texture matter again.

It's time that SM will get a different support filling system, one that doesn't close report automatically or one that Tech Support can't close as long as no real solution has been brought forth. Now the case closes after 4 days of inactivity or Tech Support can close it whenever they feel like it. Cases should only be closed when resolved.

 I'm glad I'm not in the bug squashing team. My Poser 8 has been running - along with my computer - for the past 4 days straight, and I have yet to see any Out of Memory error.

Not saying you don't see it, just that it's odd that the memory leak affects some and not all.

Most of my problems with Poser 8 at the moment is because of the stupid decimal point thing. I long to be able to enter dial values with the numerical keyboard and NOT having to use the %¤# punctuation mark just because someone forgot there's a world outside the US ;) I WANT MY COMMA BACK!

But that's my main problem atm - that and the obj importer whichb makes my Poser crash - but I am starting to suspect that is somehow related to the decimal point thing as well,  since Ratscloset couldn't replicate it, so I'll hold my breath until SR1 and hope it is solved then.

is it there yet?! 

Quote - Teaser time. More SR1 IDL goodness here. 23 minutes.

Beautifull, but ... wich configuration ? wich render settings ?

Quote - Teaser time. More SR1 IDL goodness here. 23 minutes.

Goddamit BB!  That's just mean ;)  Do you have any idea how the SR1 is coming along? Can we expect it within the next few days?

Guys, let's not confuse memory use climbing while idle with cannot load texture. These are separate issues.

I know the texture failure dialog says it could be out of memory. That's not the problem for those who see it instantly. It's because there were some bugs in dealing with file I/O (a few actually) and they've been fixed. Let's see if SR1 fixes it.

As to the climbing memory, this is normal, although it perhaps scares you. However, you've noted that most if not all the memory is given back when you minimize. It is also given back periodically. This is memory being used to cache messages going between the library GUI and Poser. It is a normal consequence of using modern "managed code" where the programmer is not responsible for memory management - the system is. This is how Flash works. Every once in a while, a garbage collector runs and gives the memory back. I watched this very carefully for hours and hours. It is not a bug when it is working as it is supposed to.

That's not to say it is impossible to consume all of memory doing nothing. There are any number of components that could be buggy in this area. I've seen graphics drivers do it, I've seen out-of-date versions of Flash and IE do it, lots of things that are under your control, not P8's control. Not saying you've done something wrong.

Sigh - I have to go on and on trying to explain these technical things. I'm sure I'm becoming boring/insulting again to somebody.