 | | | high-res mesh crashing XSI | high-res mesh crashing XSI 2004-04-19 - By David Shirk
Back
as Brad just reminded me, we tested a lot of grid resolutions from
Realwave until we hit one that would render without having to resort to
mi files.
That said, we also saved memory by stopping the grid at a distance from
camera where the wave heights were less than a pixel high and switched
to a lightweight grid that was mapped with animated noise.
Good luck guys...that viking job was fun-and-a-half =)
Dave
Rick Walia wrote:
> If I recall correctly both Brad and Dave had a problem with something like
this
> last year. I think they found a bug and a workaround or something like that.
> Dave? Brad? remember?
>
> /R
>
>
> Quoting Daniel Bachler <DanyX@(protected)>:
>
>
>>What is the memory usage when XSI crashes? if it is well above one GB you
>>might want to try the more-than-2 (See http://han-2.ora-code.com)GB of RAM startup-switch, assuming you work
>>on windows. There is a thread on xsibase that describes its usage:
>>http://www.xsibase.com/forum/index.php?board=12;action=display;threadid=1101
>>4;start=0#msg73448
>>
>>(attn, url will wrap)
>>
>>Daniel
>>
>>
>>>-- --Original Message-- --
>>>From: owner-xsi@(protected)
>>>[mailto:owner-xsi@(protected)] On Behalf Of Kris Rivel
>>>Sent: Montag, 19. April 2004 23:25
>>>To: XSI@(protected)
>>>Subject: RE: high-res mesh crashing XSI
>>>
>>>No, it needs to stay together as one mesh. Its one large ocean
>>>surface. The geometry is being updated by an external file
>>>source that RW
>>>generates. Thanks for the suggestion though.
>>>
>>>Kris
>>>
>>>At 03:59 PM 4/19/2004, you wrote:
>>>
>>>>Would it be an option to split the mesh into smaller ones
>>>
>>>(try splitting
>>>
>>>>in 2, then 4, ...)?
>>>>
>>>>-- --Original Message-- --
>>>>From: owner-xsi@(protected)
>>>
>>>[mailto:owner-xsi@(protected)]On Behalf
>>>
>>>>Of Kris Rivel
>>>>Posted At: Monday, April 19, 2004 3:23 PM
>>>>Posted To: xsi
>>>>Conversation: high-res mesh crashing XSI
>>>>Subject: high-res mesh crashing XSI
>>>>
>>>>
>>>>I have a high-res mesh around 1.1 million triangles and it will not
>>>>render....just sits there and crashes. I searched the
>>>
>>>archives and came
>>>
>>>>across a few folks who had similar issues and seemed to
>>>
>>>resolve them by
>>>
>>>>removing textures....which is not an option for me. I've
>>>
>>>tried exporting
>>>
>>>>out as an MI2 file with no success.....it will still crash.
>>>
>>>This mesh is
>>>
>>>>being generated in RealWave. I know the problem is with XSI
>>>
>>>and not RW
>>>
>>>>since freezing the mesh and removing the RW operator will
>>>
>>>still cause XSI
>>>
>>>>to crash. I've tried adjusting all memory settings and bsp
>>>
>>>settings. Any
>>>
>>>>ideas?
>>>>
>>>>Kris Rivel
>>>>Quiet Man
>>>>www.quietman.net
>>>>
>>>>
>>>>
>>>>---
>>>>Unsubscribe? Mail Majordomo@(protected) with the following
>>>
>>>text in body:
>>>
>>>>unsubscribe xsi
>>>>
>>>>---
>>>>Unsubscribe? Mail Majordomo@(protected) with the following
>>>
>>>text in body:
>>>
>>>>unsubscribe xsi
>>>
>>>
>>>---
>>>Unsubscribe? Mail Majordomo@(protected) with the following
>>>text in body:
>>>unsubscribe xsi
>>>
>>
>>---
>>Unsubscribe? Mail Majordomo@(protected) with the following text in body:
>>unsubscribe xsi
>>
>
>
>
>
> ---
> Unsubscribe? Mail Majordomo@(protected) with the following text in body:
> unsubscribe xsi
--
| David Shirk | technical animator | industrial light + magic | x3555 |
---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi
|
|
|