Module 'sprite' not found

Getting Started Newbie Questions
#1

My programs ran perfectly in the simulator. I installed the latest version and the problems started. 

I run an application and shows: 

module ‘sprite’ not found 

Module ‘sprite’ not found: resource (sprite.lu) does not exist in archive 

no field package.preload [‘sprite’] 

no file ‘/ Users / Fabio / Library / Application Support / Corona / Simulator / Plugins / sprite.lua’ 

no file ‘/ Users / Fabio / Documents / Corona Iphone ipad / First / sprite.lua’ 

no file ‘/ Applications / CoronaSDK / Corona Simulator.app / Contents / Resources / sprite.lua’ 

no file ‘/ Users / Fabio / Library / Application Support / Corona / Simulator / Plugins / sprite.dylib’ 

no file ‘. / sprite.dylib’ 

no file ‘/ Applications / CoronaSDK / Corona Simulator.app / Contents / Resources / sprite.dylib’ 

Someone can explain me what happens?

#2

See here:

http://docs.coronalabs.com/guide/graphics/migration_g20.html#removed-libraries-and-apis

You didn’t specify what build you are using or have been using, but this is likely the issue.

#3

Now:  Version 2013.2100 (2013.12.7)

I could hardly recover some data from my old computer. I do not remember the previous version.

#4

Yeah, my guess is you were using the Graphics 1.0 engine build before, and you moved up to the Graphics 2.0 engine builds.

Note that things are very different now.  You might want to take a look at this:

http://docs.coronalabs.com/guide/graphics/migration.html

#5

Also be advised that build 2100 has a bug that apps built with it do not work on Android devices with an Nvidia Tegra 2 chipset.  So you might want to consider going for a daily build instead.

#6

I find it pathetic that migration Graphics Graphics 1.0 to 2.0 the programmer has to do when it is very clear that the Graphics version 1.0 was very poor. Would that automatically make the editor. Very bad, very bad. 

Not only paid for the software, but now I have to do double work because the application that was already finished and now it does not run into problems. 

This is very serious.

#7

You can continue to use graphics 1 style features simply by putting graphicsCompatibility = 1 in your config.lua.  The Sprite library has been deprecated for a long time (over a year I believe).  That is more than enough time for people to migrate to the new way of doing sprites.

However, we realized that people will still want to use the old library (even though the new one is much better).  So we made that library available as open source on our github repository.  Just download the sprite.lua, drop it in the folder with your main.lua and you shouldn’t need any other changes.

Rob

#8

See here:

http://docs.coronalabs.com/guide/graphics/migration_g20.html#removed-libraries-and-apis

You didn’t specify what build you are using or have been using, but this is likely the issue.

#9

Now:  Version 2013.2100 (2013.12.7)

I could hardly recover some data from my old computer. I do not remember the previous version.

#10

Yeah, my guess is you were using the Graphics 1.0 engine build before, and you moved up to the Graphics 2.0 engine builds.

Note that things are very different now.  You might want to take a look at this:

http://docs.coronalabs.com/guide/graphics/migration.html

#11

Also be advised that build 2100 has a bug that apps built with it do not work on Android devices with an Nvidia Tegra 2 chipset.  So you might want to consider going for a daily build instead.

#12

I find it pathetic that migration Graphics Graphics 1.0 to 2.0 the programmer has to do when it is very clear that the Graphics version 1.0 was very poor. Would that automatically make the editor. Very bad, very bad. 

Not only paid for the software, but now I have to do double work because the application that was already finished and now it does not run into problems. 

This is very serious.

#13

You can continue to use graphics 1 style features simply by putting graphicsCompatibility = 1 in your config.lua.  The Sprite library has been deprecated for a long time (over a year I believe).  That is more than enough time for people to migrate to the new way of doing sprites.

However, we realized that people will still want to use the old library (even though the new one is much better).  So we made that library available as open source on our github repository.  Just download the sprite.lua, drop it in the folder with your main.lua and you shouldn’t need any other changes.

Rob