Re: Fuzz trouble
Its the compounds that allow hair pointclouds to deform along with animated geometry, and it does use the reinterpret node. Unfortunately its something we used a lot! If you try opening this model in 2014 it should be fine, open in 2015 and instant lock up: https://app.box.com/s/vpctkz2k1xnxxhbc1dgglhr022gkc7sh On 14 July 2015 at 09:17, wrote: > Do you know which ones? It may be that they are using the ‘reinterpret’ > node too. It would be good to collate any other 2015 issues for a final fix > push to AD. > > As to why some people on here are trying to influence me to not bother. It > seems a very odd and defeatist thing to do and its not going to work. > > Its the squeaky wheel that gets the oil. > > *From:* Matt Morris > *Sent:* Tuesday, July 14, 2015 1:15 AM > *To:* softimage@listproc.autodesk.com > *Subject:* Re: Fuzz trouble > > It also broke a few key compounds kristinka uses. I might be able to dig > up an old scene if it will help. This stopped us moving to 2015 from > 2014sp2. > > > > On 14 July 2015 at 00:55, Busty kelp wrote: > >> And AD asked me tonight for a sample scene to test. >> >> Sent from my iPad >> >> > On 13 Jul 2015, at 21:38, Matt Lind wrote: >> > >> > You overlook the fact you need to be on Softimage 2015 to get >> support. They're not going to touch 2013. >> > >> > >> > Matt >> > >> > >> > >> > >> > >> > Date: Mon, 13 Jul 2015 10:07:36 +0100 >> > From: >> > Subject: Re: Fuzz trouble >> > To: >> > >> > Well so far its taken me around half an hour of my time. >> > In my book, a 1% chance is better than a 0% chance. I'm fully expecting >> them >> > to do nothing. >> > I have a face to face meeting with AD soon, not about this issue but in >> > which I will flag this again. >> > In the very least, I have a catalogued situation of me trying to get >> this >> > fixed so I can work with the latest version and AD doing nothing about >> it. >> > I can refer to this in the future if necessary. >> > >> > I don't use 2015 I use 2013, which is fine for me, so i have nothing to >> > lose. Thanks for your concern about my welfare though. >> > >> > >> > >> >> > > > -- > www.matinai.com > -- www.matinai.com
Re: Fuzz trouble
Do you know which ones? It may be that they are using the ‘reinterpret’ node too. It would be good to collate any other 2015 issues for a final fix push to AD. As to why some people on here are trying to influence me to not bother. It seems a very odd and defeatist thing to do and its not going to work. Its the squeaky wheel that gets the oil. From: Matt Morris Sent: Tuesday, July 14, 2015 1:15 AM To: softimage@listproc.autodesk.com Subject: Re: Fuzz trouble It also broke a few key compounds kristinka uses. I might be able to dig up an old scene if it will help. This stopped us moving to 2015 from 2014sp2. On 14 July 2015 at 00:55, Busty kelp wrote: And AD asked me tonight for a sample scene to test. Sent from my iPad > On 13 Jul 2015, at 21:38, Matt Lind wrote: > > You overlook the fact you need to be on Softimage 2015 to get support. They're not going to touch 2013. > > > Matt > > > > > > Date: Mon, 13 Jul 2015 10:07:36 +0100 > From: > Subject: Re: Fuzz trouble > To: > > Well so far its taken me around half an hour of my time. > In my book, a 1% chance is better than a 0% chance. I'm fully expecting them > to do nothing. > I have a face to face meeting with AD soon, not about this issue but in > which I will flag this again. > In the very least, I have a catalogued situation of me trying to get this > fixed so I can work with the latest version and AD doing nothing about it. > I can refer to this in the future if necessary. > > I don't use 2015 I use 2013, which is fine for me, so i have nothing to > lose. Thanks for your concern about my welfare though. > > > -- www.matinai.com
RE: Fuzz trouble
I hope AD at least fix what they broke for the very last release… From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Matt Morris Sent: lunes, 13 de julio de 2015 07:15 p. m. To: softimage@listproc.autodesk.com Subject: Re: Fuzz trouble It also broke a few key compounds kristinka uses. I might be able to dig up an old scene if it will help. This stopped us moving to 2015 from 2014sp2. On 14 July 2015 at 00:55, Busty kelp mailto:p...@bustykelp.com> > wrote: And AD asked me tonight for a sample scene to test. Sent from my iPad > On 13 Jul 2015, at 21:38, Matt Lind <mailto:speye...@hotmail.com> > wrote: > > You overlook the fact you need to be on Softimage 2015 to get support. > They're not going to touch 2013. > > > Matt > > > > > > Date: Mon, 13 Jul 2015 10:07:36 +0100 > From: mailto:p...@bustykelp.com> > > Subject: Re: Fuzz trouble > To: mailto:softimage@listproc.autodesk.com> > > > > Well so far its taken me around half an hour of my time. > In my book, a 1% chance is better than a 0% chance. I'm fully expecting them > to do nothing. > I have a face to face meeting with AD soon, not about this issue but in > which I will flag this again. > In the very least, I have a catalogued situation of me trying to get this > fixed so I can work with the latest version and AD doing nothing about it. > I can refer to this in the future if necessary. > > I don't use 2015 I use 2013, which is fine for me, so i have nothing to > lose. Thanks for your concern about my welfare though. > > > -- www.matinai.com <http://www.matinai.com>
Re: Fuzz trouble
It also broke a few key compounds kristinka uses. I might be able to dig up an old scene if it will help. This stopped us moving to 2015 from 2014sp2. On 14 July 2015 at 00:55, Busty kelp wrote: > And AD asked me tonight for a sample scene to test. > > Sent from my iPad > > > On 13 Jul 2015, at 21:38, Matt Lind wrote: > > > > You overlook the fact you need to be on Softimage 2015 to get support. > They're not going to touch 2013. > > > > > > Matt > > > > > > > > > > > > Date: Mon, 13 Jul 2015 10:07:36 +0100 > > From: > > Subject: Re: Fuzz trouble > > To: > > > > Well so far its taken me around half an hour of my time. > > In my book, a 1% chance is better than a 0% chance. I'm fully expecting > them > > to do nothing. > > I have a face to face meeting with AD soon, not about this issue but in > > which I will flag this again. > > In the very least, I have a catalogued situation of me trying to get this > > fixed so I can work with the latest version and AD doing nothing about > it. > > I can refer to this in the future if necessary. > > > > I don't use 2015 I use 2013, which is fine for me, so i have nothing to > > lose. Thanks for your concern about my welfare though. > > > > > > > > -- www.matinai.com
Re: Fuzz trouble
And AD asked me tonight for a sample scene to test. Sent from my iPad > On 13 Jul 2015, at 21:38, Matt Lind wrote: > > You overlook the fact you need to be on Softimage 2015 to get support. > They're not going to touch 2013. > > > Matt > > > > > > Date: Mon, 13 Jul 2015 10:07:36 +0100 > From: > Subject: Re: Fuzz trouble > To: > > Well so far its taken me around half an hour of my time. > In my book, a 1% chance is better than a 0% chance. I'm fully expecting them > to do nothing. > I have a face to face meeting with AD soon, not about this issue but in > which I will flag this again. > In the very least, I have a catalogued situation of me trying to get this > fixed so I can work with the latest version and AD doing nothing about it. > I can refer to this in the future if necessary. > > I don't use 2015 I use 2013, which is fine for me, so i have nothing to > lose. Thanks for your concern about my welfare though. > > >
Re: Fuzz trouble
I don't overlook it. I have my studio subscription up to 2015. I just don't use it because of this issue. Why would I want them to touch 2013? It works fine. Sent from my iPad > On 13 Jul 2015, at 21:38, Matt Lind wrote: > > You overlook the fact you need to be on Softimage 2015 to get support. > They're not going to touch 2013. > > > Matt > > > > > > Date: Mon, 13 Jul 2015 10:07:36 +0100 > From: > Subject: Re: Fuzz trouble > To: > > Well so far its taken me around half an hour of my time. > In my book, a 1% chance is better than a 0% chance. I'm fully expecting them > to do nothing. > I have a face to face meeting with AD soon, not about this issue but in > which I will flag this again. > In the very least, I have a catalogued situation of me trying to get this > fixed so I can work with the latest version and AD doing nothing about it. > I can refer to this in the future if necessary. > > I don't use 2015 I use 2013, which is fine for me, so i have nothing to > lose. Thanks for your concern about my welfare though. > > >
Re: Fuzz trouble
You overlook the fact you need to be on Softimage 2015 to get support. They're not going to touch 2013. Matt Date: Mon, 13 Jul 2015 10:07:36 +0100 From: Subject: Re: Fuzz trouble To: Well so far its taken me around half an hour of my time. In my book, a 1% chance is better than a 0% chance. I'm fully expecting them to do nothing. I have a face to face meeting with AD soon, not about this issue but in which I will flag this again. In the very least, I have a catalogued situation of me trying to get this fixed so I can work with the latest version and AD doing nothing about it. I can refer to this in the future if necessary. I don't use 2015 I use 2013, which is fine for me, so i have nothing to lose. Thanks for your concern about my welfare though.
Re: Fuzz trouble
Well so far its taken me around half an hour of my time. In my book, a 1% chance is better than a 0% chance. I'm fully expecting them to do nothing. I have a face to face meeting with AD soon, not about this issue but in which I will flag this again. In the very least, I have a catalogued situation of me trying to get this fixed so I can work with the latest version and AD doing nothing about it. I can refer to this in the future if necessary. I don't use 2015 I use 2013, which is fine for me, so i have nothing to lose. Thanks for your concern about my welfare though. -Original Message- From: Matt Lind Sent: Sunday, July 12, 2015 6:07 PM To: softimage@listproc.autodesk.com Subject: Re: Fuzz trouble Let's look at facts: - The last service pack had a total of 9 bug fixes for a one year development cycle. - Some of the fixed bugs weren't exactly high priority issues. - One developer is doing any work on the product to fix those bugs. - That one developer was not part of the core development team that originated the product. - Autodesk's definition of 'support' doesn't match everybody else's definition of support. Unless you can prove your bug is seriously impacting/blocking production, don't expect anybody to put eyes on the problem. Resellers only have influence with development when there is an opportunity for a sale (or impacts retention of big customer). Since Softimage is a retired product, there is no opportunity for sale and no worry of retention. Therefore no real incentive for the bug to be fixed. You can report and chase it all you want, but it's not worth the trouble. You'll only be frustrated in the end. I should know, I've reported and chased a ton of issues to Softimage over the past 20 years. Even during the best of times it was a steep uphill battle. Your best option is to move to a version of Softimage where the bug doesn't exist, or develop your own node to replace the functionality. Matt Date: Sun, 12 Jul 2015 13:52:50 +0100 From: Busty kelp Subject: Re: Fuzz trouble To: "softimage@listproc.autodesk.com" Reinterpret location to new geometry is broken. What's for certain is that they won't fix it if nobody makes a fuss. I have my reseller chasing it up with them. It's a good time to add an extra note to them . They actually still have an obligation to fix it if they are made aware enough about it. I'm sure they want to make sure they are within their side of the contract. After all, they wouldn't want to and set a bad example and encourage us to go breaking contracts with them willy nilly. Sent from my iPad
Re: Fuzz trouble
Let's look at facts: - The last service pack had a total of 9 bug fixes for a one year development cycle. - Some of the fixed bugs weren't exactly high priority issues. - One developer is doing any work on the product to fix those bugs. - That one developer was not part of the core development team that originated the product. - Autodesk's definition of 'support' doesn't match everybody else's definition of support. Unless you can prove your bug is seriously impacting/blocking production, don't expect anybody to put eyes on the problem. Resellers only have influence with development when there is an opportunity for a sale (or impacts retention of big customer). Since Softimage is a retired product, there is no opportunity for sale and no worry of retention. Therefore no real incentive for the bug to be fixed. You can report and chase it all you want, but it's not worth the trouble. You'll only be frustrated in the end. I should know, I've reported and chased a ton of issues to Softimage over the past 20 years. Even during the best of times it was a steep uphill battle. Your best option is to move to a version of Softimage where the bug doesn't exist, or develop your own node to replace the functionality. Matt Date: Sun, 12 Jul 2015 13:52:50 +0100 From: Busty kelp Subject: Re: Fuzz trouble To: "softimage@listproc.autodesk.com" Reinterpret location to new geometry is broken. What's for certain is that they won't fix it if nobody makes a fuss. I have my reseller chasing it up with them. It's a good time to add an extra note to them . They actually still have an obligation to fix it if they are made aware enough about it. I'm sure they want to make sure they are within their side of the contract. After all, they wouldn't want to and set a bad example and encourage us to go breaking contracts with them willy nilly. Sent from my iPad
Re: Fuzz trouble
Reinterpret location to new geometry is broken. What's for certain is that they won't fix it if nobody makes a fuss. I have my reseller chasing it up with them. It's a good time to add an extra note to them . They actually still have an obligation to fix it if they are made aware enough about it. I'm sure they want to make sure they are within their side of the contract. After all, they wouldn't want to and set a bad example and encourage us to go breaking contracts with them willy nilly. Sent from my iPad > On 11 Jul 2015, at 22:59, Mario Reitbauer wrote: > > There wont be fixes anymore, quite sure about that. > You might get a new logo for the next "release" that's it, and only if the > design guy needs to be annoyed cause he got nothing to do. > > 2015-07-11 23:45 GMT+02:00 Mirko Jankovic : >> do you really think that they haven't signed off SI like a year ago even.. >> and that they have anyone at all paying a bit of attention to Si at all >> they haven;t even when it was kinda developed... >> >>> On Sat, Jul 11, 2015 at 9:41 PM, Ognjen Vukovic wrote: >>> Could you explain what exactly to flag? What nodes are broken and whats >>> going on under the hood, i think it would be easier if we could consolidate >>> around that. >>> On Sat, Jul 11, 2015 at 5:46 PM, Busty kelp wrote: Please flag this as a bug with AD. I have, and I've asked others to because if enough people cause a fuss they might find a way of fixing it before signing 2015 off for good. Sent from my iPad > On 11 Jul 2015, at 11:25, Ognjen Vukovic wrote: > > Seems to be working flawlessly. Time to roll back i guess :| > > Thanks again for the heads up. > >> On Sat, Jul 11, 2015 at 12:22 PM, Ognjen Vukovic >> wrote: >> Hmmm , Im trying to open the scenes and its still a bit hit and miss. So >> i presume you might be right about that. i will have to test it out. >> Thanks. Ill get back as soon as i test out 14. >> >>> On Sat, Jul 11, 2015 at 12:02 PM, Matt Morris wrote: >>> Are you using 2015? Autodesk managed to break a few essential compounds >>> that are used in fuzz I think, best off using 2014 sp2. >>> >>> >>> On Saturday, 11 July 2015, Ognjen Vukovic wrote: Ok , for some reason having the viewport work in texture decal mode is the only way i can get it to display without hanging xsi, must be down to my gpu or something. > On Sat, Jul 11, 2015 at 12:58 AM, Ognjen Vukovic > wrote: > Has anyone encountered crashes when using fuzz when trying to unhide > the hair? I cant seem to have it unhidden at all, i tried setting > density and segments to 1/1 but still every time i try to view it in > the viewport, bang, its all gone. This is strange because last night > i was working on it with a density of 50 and 4 segments, and all was > fine, but today i cant get to my work... > > Its all a bit frustrating really, but im not sure where to take it > from here. >>> >>> >>> -- >>> www.matinai.com > > > > -- > -- > cont...@marioreitbauer.com > 0049 (0)157 86272215 > Professor-Brix-Weg 9 > 22767 Hamburg > --
Re: Fuzz trouble
There wont be fixes anymore, quite sure about that. You might get a new logo for the next "release" that's it, and only if the design guy needs to be annoyed cause he got nothing to do. 2015-07-11 23:45 GMT+02:00 Mirko Jankovic : > do you really think that they haven't signed off SI like a year ago even.. > and that they have anyone at all paying a bit of attention to Si at all > they haven;t even when it was kinda developed... > > On Sat, Jul 11, 2015 at 9:41 PM, Ognjen Vukovic wrote: > >> Could you explain what exactly to flag? What nodes are broken and whats >> going on under the hood, i think it would be easier if we could consolidate >> around that. >> >> On Sat, Jul 11, 2015 at 5:46 PM, Busty kelp wrote: >> >>> Please flag this as a bug with AD. I have, and I've asked others to >>> because if enough people cause a fuss they might find a way of fixing it >>> before signing 2015 off for good. >>> >>> Sent from my iPad >>> >>> On 11 Jul 2015, at 11:25, Ognjen Vukovic wrote: >>> >>> Seems to be working flawlessly. Time to roll back i guess :| >>> >>> Thanks again for the heads up. >>> >>> On Sat, Jul 11, 2015 at 12:22 PM, Ognjen Vukovic >>> wrote: >>> Hmmm , Im trying to open the scenes and its still a bit hit and miss. So i presume you might be right about that. i will have to test it out. Thanks. Ill get back as soon as i test out 14. On Sat, Jul 11, 2015 at 12:02 PM, Matt Morris wrote: > Are you using 2015? Autodesk managed to break a few essential > compounds that are used in fuzz I think, best off using 2014 sp2. > > > > On Saturday, 11 July 2015, Ognjen Vukovic wrote: > >> Ok , for some reason having the viewport work in texture decal mode >> is the only way i can get it to display without hanging xsi, must be down >> to my gpu or something. >> >> On Sat, Jul 11, 2015 at 12:58 AM, Ognjen Vukovic >> wrote: >> >>> Has anyone encountered crashes when using fuzz when trying to unhide >>> the hair? I cant seem to have it unhidden at all, i tried setting >>> density >>> and segments to 1/1 but still every time i try to view it in the >>> viewport, >>> bang, its all gone. This is strange because last night i was working on >>> it >>> with a density of 50 and 4 segments, and all was fine, but today i cant >>> get >>> to my work... >>> >>> Its all a bit frustrating really, but im not sure where to take it >>> from here. >>> >>> >> > > -- > www.matinai.com > >>> >> > -- -- cont...@marioreitbauer.com 0049 (0)157 86272215 Professor-Brix-Weg 9 22767 Hamburg --
Re: Fuzz trouble
do you really think that they haven't signed off SI like a year ago even.. and that they have anyone at all paying a bit of attention to Si at all they haven;t even when it was kinda developed... On Sat, Jul 11, 2015 at 9:41 PM, Ognjen Vukovic wrote: > Could you explain what exactly to flag? What nodes are broken and whats > going on under the hood, i think it would be easier if we could consolidate > around that. > > On Sat, Jul 11, 2015 at 5:46 PM, Busty kelp wrote: > >> Please flag this as a bug with AD. I have, and I've asked others to >> because if enough people cause a fuss they might find a way of fixing it >> before signing 2015 off for good. >> >> Sent from my iPad >> >> On 11 Jul 2015, at 11:25, Ognjen Vukovic wrote: >> >> Seems to be working flawlessly. Time to roll back i guess :| >> >> Thanks again for the heads up. >> >> On Sat, Jul 11, 2015 at 12:22 PM, Ognjen Vukovic >> wrote: >> >>> Hmmm , Im trying to open the scenes and its still a bit hit and miss. So >>> i presume you might be right about that. i will have to test it out. >>> Thanks. Ill get back as soon as i test out 14. >>> >>> On Sat, Jul 11, 2015 at 12:02 PM, Matt Morris wrote: >>> Are you using 2015? Autodesk managed to break a few essential compounds that are used in fuzz I think, best off using 2014 sp2. On Saturday, 11 July 2015, Ognjen Vukovic wrote: > Ok , for some reason having the viewport work in texture decal mode is > the only way i can get it to display without hanging xsi, must be down to > my gpu or something. > > On Sat, Jul 11, 2015 at 12:58 AM, Ognjen Vukovic > wrote: > >> Has anyone encountered crashes when using fuzz when trying to unhide >> the hair? I cant seem to have it unhidden at all, i tried setting density >> and segments to 1/1 but still every time i try to view it in the >> viewport, >> bang, its all gone. This is strange because last night i was working on >> it >> with a density of 50 and 4 segments, and all was fine, but today i cant >> get >> to my work... >> >> Its all a bit frustrating really, but im not sure where to take it >> from here. >> >> > -- www.matinai.com >>> >>> >> >
Re: Fuzz trouble
Could you explain what exactly to flag? What nodes are broken and whats going on under the hood, i think it would be easier if we could consolidate around that. On Sat, Jul 11, 2015 at 5:46 PM, Busty kelp wrote: > Please flag this as a bug with AD. I have, and I've asked others to > because if enough people cause a fuss they might find a way of fixing it > before signing 2015 off for good. > > Sent from my iPad > > On 11 Jul 2015, at 11:25, Ognjen Vukovic wrote: > > Seems to be working flawlessly. Time to roll back i guess :| > > Thanks again for the heads up. > > On Sat, Jul 11, 2015 at 12:22 PM, Ognjen Vukovic > wrote: > >> Hmmm , Im trying to open the scenes and its still a bit hit and miss. So >> i presume you might be right about that. i will have to test it out. >> Thanks. Ill get back as soon as i test out 14. >> >> On Sat, Jul 11, 2015 at 12:02 PM, Matt Morris wrote: >> >>> Are you using 2015? Autodesk managed to break a few essential compounds >>> that are used in fuzz I think, best off using 2014 sp2. >>> >>> >>> >>> On Saturday, 11 July 2015, Ognjen Vukovic wrote: >>> Ok , for some reason having the viewport work in texture decal mode is the only way i can get it to display without hanging xsi, must be down to my gpu or something. On Sat, Jul 11, 2015 at 12:58 AM, Ognjen Vukovic wrote: > Has anyone encountered crashes when using fuzz when trying to unhide > the hair? I cant seem to have it unhidden at all, i tried setting density > and segments to 1/1 but still every time i try to view it in the viewport, > bang, its all gone. This is strange because last night i was working on it > with a density of 50 and 4 segments, and all was fine, but today i cant > get > to my work... > > Its all a bit frustrating really, but im not sure where to take it > from here. > > >>> >>> -- >>> www.matinai.com >>> >> >> >
Re: Fuzz trouble
Please flag this as a bug with AD. I have, and I've asked others to because if enough people cause a fuss they might find a way of fixing it before signing 2015 off for good. Sent from my iPad > On 11 Jul 2015, at 11:25, Ognjen Vukovic wrote: > > Seems to be working flawlessly. Time to roll back i guess :| > > Thanks again for the heads up. > >> On Sat, Jul 11, 2015 at 12:22 PM, Ognjen Vukovic wrote: >> Hmmm , Im trying to open the scenes and its still a bit hit and miss. So i >> presume you might be right about that. i will have to test it out. >> Thanks. Ill get back as soon as i test out 14. >> >>> On Sat, Jul 11, 2015 at 12:02 PM, Matt Morris wrote: >>> Are you using 2015? Autodesk managed to break a few essential compounds >>> that are used in fuzz I think, best off using 2014 sp2. >>> >>> >>> On Saturday, 11 July 2015, Ognjen Vukovic wrote: Ok , for some reason having the viewport work in texture decal mode is the only way i can get it to display without hanging xsi, must be down to my gpu or something. > On Sat, Jul 11, 2015 at 12:58 AM, Ognjen Vukovic > wrote: > Has anyone encountered crashes when using fuzz when trying to unhide the > hair? I cant seem to have it unhidden at all, i tried setting density and > segments to 1/1 but still every time i try to view it in the viewport, > bang, its all gone. This is strange because last night i was working on > it with a density of 50 and 4 segments, and all was fine, but today i > cant get to my work... > > Its all a bit frustrating really, but im not sure where to take it from > here. >>> >>> >>> -- >>> www.matinai.com >
Re: Fuzz trouble
Seems to be working flawlessly. Time to roll back i guess :| Thanks again for the heads up. On Sat, Jul 11, 2015 at 12:22 PM, Ognjen Vukovic wrote: > Hmmm , Im trying to open the scenes and its still a bit hit and miss. So i > presume you might be right about that. i will have to test it out. > Thanks. Ill get back as soon as i test out 14. > > On Sat, Jul 11, 2015 at 12:02 PM, Matt Morris wrote: > >> Are you using 2015? Autodesk managed to break a few essential compounds >> that are used in fuzz I think, best off using 2014 sp2. >> >> >> >> On Saturday, 11 July 2015, Ognjen Vukovic wrote: >> >>> Ok , for some reason having the viewport work in texture decal mode is >>> the only way i can get it to display without hanging xsi, must be down to >>> my gpu or something. >>> >>> On Sat, Jul 11, 2015 at 12:58 AM, Ognjen Vukovic >>> wrote: >>> Has anyone encountered crashes when using fuzz when trying to unhide the hair? I cant seem to have it unhidden at all, i tried setting density and segments to 1/1 but still every time i try to view it in the viewport, bang, its all gone. This is strange because last night i was working on it with a density of 50 and 4 segments, and all was fine, but today i cant get to my work... Its all a bit frustrating really, but im not sure where to take it from here. >>> >> >> -- >> www.matinai.com >> > >
Re: Fuzz trouble
Hmmm , Im trying to open the scenes and its still a bit hit and miss. So i presume you might be right about that. i will have to test it out. Thanks. Ill get back as soon as i test out 14. On Sat, Jul 11, 2015 at 12:02 PM, Matt Morris wrote: > Are you using 2015? Autodesk managed to break a few essential compounds > that are used in fuzz I think, best off using 2014 sp2. > > > > On Saturday, 11 July 2015, Ognjen Vukovic wrote: > >> Ok , for some reason having the viewport work in texture decal mode is >> the only way i can get it to display without hanging xsi, must be down to >> my gpu or something. >> >> On Sat, Jul 11, 2015 at 12:58 AM, Ognjen Vukovic >> wrote: >> >>> Has anyone encountered crashes when using fuzz when trying to unhide the >>> hair? I cant seem to have it unhidden at all, i tried setting density and >>> segments to 1/1 but still every time i try to view it in the viewport, >>> bang, its all gone. This is strange because last night i was working on it >>> with a density of 50 and 4 segments, and all was fine, but today i cant get >>> to my work... >>> >>> Its all a bit frustrating really, but im not sure where to take it from >>> here. >>> >>> >> > > -- > www.matinai.com >
Re: Fuzz trouble
Are you using 2015? Autodesk managed to break a few essential compounds that are used in fuzz I think, best off using 2014 sp2. On Saturday, 11 July 2015, Ognjen Vukovic wrote: > Ok , for some reason having the viewport work in texture decal mode is the > only way i can get it to display without hanging xsi, must be down to my > gpu or something. > > On Sat, Jul 11, 2015 at 12:58 AM, Ognjen Vukovic > wrote: > >> Has anyone encountered crashes when using fuzz when trying to unhide the >> hair? I cant seem to have it unhidden at all, i tried setting density and >> segments to 1/1 but still every time i try to view it in the viewport, >> bang, its all gone. This is strange because last night i was working on it >> with a density of 50 and 4 segments, and all was fine, but today i cant get >> to my work... >> >> Its all a bit frustrating really, but im not sure where to take it from >> here. >> >> > -- www.matinai.com
Re: Fuzz trouble
Ok , for some reason having the viewport work in texture decal mode is the only way i can get it to display without hanging xsi, must be down to my gpu or something. On Sat, Jul 11, 2015 at 12:58 AM, Ognjen Vukovic wrote: > Has anyone encountered crashes when using fuzz when trying to unhide the > hair? I cant seem to have it unhidden at all, i tried setting density and > segments to 1/1 but still every time i try to view it in the viewport, > bang, its all gone. This is strange because last night i was working on it > with a density of 50 and 4 segments, and all was fine, but today i cant get > to my work... > > Its all a bit frustrating really, but im not sure where to take it from > here. > >
Fuzz trouble
Has anyone encountered crashes when using fuzz when trying to unhide the hair? I cant seem to have it unhidden at all, i tried setting density and segments to 1/1 but still every time i try to view it in the viewport, bang, its all gone. This is strange because last night i was working on it with a density of 50 and 4 segments, and all was fine, but today i cant get to my work... Its all a bit frustrating really, but im not sure where to take it from here.
