I got this error and I am not sure if its new or not but it is definitely new for me (I think :-\)
anyways...I really like how this scene is turning out and this error is not making me happy.... >:(
This might be the best character I've seen TG2 do and that's probably the reason for the error. I'm not sure how it works, but somehow TG2 has run out of memory. Hopefully, this will be adequately addressed before the Final.
character??...what character???.....thats my wallpaper calico.....
That's a memory-related error, usually to do with image maps you may be loading. What does your scene consist of?
- Oshyan
yea I get that a lot, even with four gigs sadly.
there are only 2 image maps...
1. image map for the tree population...
2. image map used as mask for the river....
but I deleted the population and I still get the error......so that cant be the bark image map
but then it was working fine before I added the population....so that cant be the mask image map either.....
so...I have no clue whats going on....
How large are the image maps and how much RAM do you have? Any other applications running?
- Oshyan
I have 4GB RAM
mask image map: 4097 x 4097
bark image map: 500 x 4500
no applications running.......
File size and format of mask images? Any other demanding bits of the scene? How big is the population?
- Oshyan
population is 15000 x 15000
Spacing? How many instances? ;) Also I presume this is on a 32 bit OS so really only 2GB is available to the app even though you have 4.
- Oshyan
no I am using 64-bit Vista and the spacing was 50 and I increased the object scale to about 10, 10 ,10
You've got me stumped then. ;D
- Oshyan
Quote from: dhavalmistry on October 19, 2007, 04:01:50 PM
character??...what character???.....thats my wallpaper calico.....
;D ;D ;D
Quote from: seth93 on October 19, 2007, 06:35:15 PM
Quote from: dhavalmistry on October 19, 2007, 04:01:50 PM
character??...what character???.....thats my wallpaper calico.....
;D ;D ;D
ya its friday evening...I understand...:D:D
that Jade Empire?
no its Heavenly Sword for PS3...beautiful game....
Hi,
I'm not sure that running TG2 on 64 bit Vista is going to make much difference to how much memory it can use, because TG2 is still 32 bit. I don't know if 32 bit apps on 64 bit Windows get the whole 4 GB of the 32 bit address space to themselves, seeing as the OS could move it's memory out of the app's address space, but they may not for compatibility reasons.
Regards,
Jo
**UPDATE**
I deleted the population that was causing trouble and added a new population of different trees and it seems to be working for now...no problems so far...
HAHAHAHAAHAHAHAHAHAHA.
Sorry. :-[
Quote from: dhavalmistry on October 19, 2007, 04:01:50 PM
character??...what character???.....thats my wallpaper calico.....
somebody PLEASSSSEEEEEEE fix this error....I am getting sick an tired of it ruining my every scene >:( >:( >:( >:( >:(
Hi,
Quote from: dhavalmistry on October 20, 2007, 11:57:09 AM
somebody PLEASSSSEEEEEEE fix this error....I am getting sick an tired of it ruining my every scene >:( >:( >:( >:( >:(
As I have described somewhere before, while it is an error, it is not really an error on TG2s part. You are trying to exceed what can be done, TG2 cannot allocate the memory you are asking it to. It is letting you know that something serious has taken place. This is a good thing - if TG2 didn't check for this sort of thing the alternative would be for the application to just crash, and I think you'd agree that isn't desirable. TG2 is doing the right thing.
Most of the errors that come up in the Errors and Warnings window are not because TG2 has done something wrong, but instead it is letting you know that it is not doing something because it can't.
It is true that we could do some things to improve situations like this. We can make TG2 use memory in different ways so that more images or whatever can be loaded at once, although that is likely to degrade performance a bit. It isn't an overnight fix though. On a 32 bit OS it is always going to be possible to push TG2 farther than it can go with respect to system resources, a 64 bit version would push the limits back further. As things stand though, this probably isn't something which can just be fixed, and on the surface it isn't a bug.
It could be that something is going wrong, but we cannot tell what it might be from the information you've given. It sounds from your very minimal description that things should be working, but we would need the entire scene to be able to check it out.
Regards,
Jo