Voidwatch, the Xbox360 and its issues/bugs.

[Greatguardian]

Translation: Yes, it really is a much more complex issue than people have assumed.

noit'snot.

Their memoized cache was getting too big for the 360 because it happens to share system/graphical RAM (PCs and PS3s do not, and PS2 plays at a lower resolution). The 360 only has 512MB of RAM compared to PS2's 256MB, overall not a huge jump in active memory even though it's generally a more powerful console.

The issue is extremely simple to look at, but extremely difficult to fix because you're basically forced to say "Well. The 360 is straight up too weak to handle all these animations in the memoized cache at the same time. Wat do?"

The easiest solution would be to start lowering the resolution that 360 players can play at, which a reasonable person might understand because, frankly, the console isn't strong enough any more, but unfortunately the majority of players are not reasonable and I'm sure this would never get cleared by management.

Beyond that, they either need to find a way to flush the memo more often (creating more strain on the processor and hard drive, which may not help at all), or reduce the file size of the textures being pulled by the game and stored in the memo without affecting their apparent resolution (Which may not even be a permanent fix).

I do not envy the programmers assigned to this.

[hideka]

so basical he is trying to say that a current generation system cant handle the specs of a PREVIOUS generations game? i smell bull. i think they dont know their ass from their elbow and the result is our current situation.

[Robmelee]

Basically, for the time being until the Development team can produce a viable solution for this Xbox 360 problem for VoidWatch;

us Xbox 360 players that are regularly involved in VoidWatch (multiple-runs) in the same zone will have to either log off and log back in or leave the zone and come back in (if a zone exit is near by) every one or two battles to reduce odds of Xbox 360 console terminations (freezes) by 100% if you choose to re-log/re-zone every battle OR by 85% if you choose to re-log/re-zone every two battles.

Just last night I was doing the VW Jueno T3 "Pil" run x12, and I re-zoned every two battles and never crashed once. But on different runs before when I wasn't zoning or re-logging I would crash most certainly by the 3rd or at the latest 4th battle.

Just FYI; Xbox 360 users going for entire VW Tier clears need not to take these temporary measures since "clear" runs only involves the killing of each mob once and moving on the next zone mob thus clearing the temp memory on Xbox 360 that the Producer just mention.

I hope all that I just said was at all helpful. Peace!

[hideka]

hey, heres an idea. wow did this back almost a decade ago. /reload. produces the effect of "zoning" and reloads you in the same position. this resets any UI bugs, or world bugs client side. wouldnt be hard to do since tractor can already do this.

[hideka]

and i get the same issues on PC, but never crash, just massive stacking lag after the second battle is over.

[Frost]

I'm just really glad they gave actual information, and not the usual brush off.

Thank you for giving us the straight answer SE, and not talking down to us like we're all idiots.

[Greatguardian]

I'm just really glad they gave actual information, and not the usual brush off.

Thank you for giving us the straight answer SE, and not talking down to us like we're all idiots.

No kidding. It's much appreciated.

@Hideka: There's a reason programmers use memoization in the first place.

[HimuraKenshyn]

What if you turn most of the effects off from the config? would that alleviate the issue some what it shouldn't have to load them if not displaying them.

[wish12oz]

hey, heres an idea. wow did this back almost a decade ago. /reload.

I have a better idea, spend $100 and get a PC that runs FFXI better then a PS2 or 360 so SE can discontinue support for them.

[hideka]

i play on PC lol >_>