do non tegra devices work on the android version?

because i have a rooted nook color and want to know if that can run it :(

it runs at 1.1 ghz

and i also want to know when vendetta will be released.

ps i can also run dungeon defenders at full speed if that helps tell my specs.

I don't suppose you've actually bothered to look around yourself?
http://www.vendetta-online.com/x/msgboard/7/24361
There you go, it should answer it as full as anyone other than a dev can.

The nook is a great device, but vendeta is going to need the dual core power of the tegra, and the gpu abilities and instruction set that is not found in the power vr gpu in the nook color

i mean like will it even allow non tegra devices to open the app??

idk if i get 3 fps all i realy want to do is talk to people via the nook

i know itll run it .

but do they actualy say you have to have tegra or it wont even let you install it?

dont know, as a guess, id say not, but when it launches,Ill test it out. I have both, and I can put the vendetta data from the xoom onto the nook and see if it will work that way. My quess is that it wont even load though, Vendetta is using a shader language the the powervr gpu doesnt support

ok so i altered my Nooks build prop so market thinks its a xoom,loaded up the game and....worse then a slide show, the opening movie froze my nook

Heh. Thanks for the report.

Im assuming you focused on tegra because its gpu is a modified variant of what a standard pc would use, correct? I have done some exploring, and some netbooks use the same gpu found in the galaxy s series of devices, and they artifact badly when playing vendetta

Actually, tegra is an ARM architecture, so definately NOT what you'd find in ANY home pc. I'm pretty sure they chose tegra because it's the first ARM processor with enough juice to crank out gameplay.

Up till now VO was only compiled for x86 and amd64 architectures, ARM is completely different from either of those.

The Tegra2 has a gpu that's comparable to a PC of about 6 or so years ago, so it is the first mobile device with the graphics capability to run the game at a decent quality.

jackjx: the issues on netbooks with the "Intel Z500" gpu (similar to the Galaxy Tab gpu) are entirely because of Intel's drivers, not due to any specific problem on the gpu or the game.

We may eventually support non-tegra devices, but there are some technical caveats. In the near term a Tegra-2 device will be required to get a good gameplay experience on Android.

jackxlj can you explain how you edited the build.prop to get it to show up in the market? I tried replacing my adam's build.prop with the xooms but it still doesnt appear in the market

@raybondo: While I know well that you have to focus on one device family for mobile Vendetta, and that iOS support is but a distant dream at this time :-) , power-wise, the iPad 2's dual Cortex A9/PowerVR SGX 543MP2 might be more than adequate for VO, as it apparently stomps the Tegra 2 into subterranean territory ;-) :

http://www.tipb.com/2011/03/13/apple-a5-dual-cortex-a9-powervr-sgx-543mp2/

That said, I think Android is the perfect base for expanding VO into mobile territory.

Yeah, the hardware for the ipad2 is probably fast enough but it has only 512 megs of ram which generally isn't enough for vendetta.

Fascinating. That the first we've seen of it running on a Galaxy S. I ran it on a pre-production Nexus S back in December when I was out at Google, but there were a lot of rendering problems. The hardware of a Nexus S should be fast enough, the issue is that we don't have a PowerVR-compressed asset pack as of yet, nor have we done much testing on anything but Tegra.

And, very obviously the game's interface is not well suited to phones right now.

raybondo, out of curiosity, why wouldn't 512 megs of RAM be enough for Vendetta? Your minimum system requirements state less than that for Mac, Windows, and Linux- which I would think would have less free RAM by default just because of the OS..

512MB should be enough for Vendetta. The issue is more of how the OS handles background applications. On a PC, you have "virtual memory", or swap. If the system runs out of memory, it swaps background apps out to disk. This doesn't happen on Android or iOS, instead the OS is supposed to quietly kill background apps when needed. However, other game developers have told us that, for the iPad 1 anyway, this does not work well, and Apple tells them vaguely to "allocate memory slowly". This isn't really much of a solution for a game developer.

Android isn't perfect in this area either, and that's part of why we prefer devices with 1GB of ram, like the Xoom. People's expectations are that apps will just work when fired up, but if the OS can't make the memory available quickly enough, bad things can happen, and the users end up blaming the game developer (since that's the "app that crashed", as opposed to the 37 things they have running in the background, hogging all the memory).

The only elegant solution we've seen so far is to do some testing on startup and basically fire off a window to the user saying "Not enough free memory, close background apps or reboot the device". But even the detection of free memory on some of these systems can be problematic.