Language…
15 users online:  AmperSam,  Anorakun, Beed28, DanMario24YT, gizmo_321, Golden Yoshi, Gorry, h.carrell, Hammerer, OrangeBronzeDaisy, Papangu, Serge, signature_steve, SMW Magic, Spedinja - Guests: 265 - Bots: 394
Users: 64,795 (2,370 active)
Latest user: mathew

Problems with PIXI 1.2.1

Hello good morning, today I come to here because I have a problem with PIXI 1.2.1, after installing it when I will proceed to install the custom sprites to my hack (those of the new generation), when it sends me to place the name of my ROM (example SMW.smc) appear this Message

"terminated called after throwing an instance of 'std::invalid_argument´"

"This application has requested the Runtime to terminate it an usual way. Please contact the application´s support team for more information"
and later the program closes (Crash).

I thought that it was because NetFramework3.5 didn't have in my Windows 8, as I don't have internet to discharge it, I decided to prove with Windows XP (VirtualBox), I Already have the installer of NETFrameWork3.5 (Offline Installer) for this system, after making the whole process install the program etc, after making all PIXI 1.2.1 !close alone! (here we are in Windows XP), not you that it happens, if this continuous I will use the old Romi´s Sprite Tool. (Also install many Libraries of C++ 2008,9,15,13 etc.)

Not you if I lacked some other program..... Friends seriously help me this new Sprite Tool it is interesting, he/she wanted to prove it.... (without mentioning that most of the custom sprites of it paginates it they are for this program)

I in my laptop use am Windows 8 Professional 32 Bits
and in the VirtualBox I use Windows XP Professional SP3 32 Bits

I have their help! :D

PD: Sorry my bad English :P
This happened me a few times and generally happened with a faulty list.txt and sometimes with a broken JSON file. Can we see how it looks?

Also, if this is a new ROM, I recommend you to use GIEPY. We will soon switch to that due to the issues with PIXI we had (no, not the error you got but some other problems).
Nice program thanks! (Is compatible with old custom sprites like old mikeyk sprites, Jap sprite packs, data.zip etc).

But..... ¿I how convert Pixi sprites to Gipeyi, the pixi sprites not are compatible... D:

Please helppp!!!!

PD: sorry my bad english yo hablo es español :)
@Terios go ther https://boldowa.github.io/GIEPY/
Se usan en efectivo, pero debe convertirlos en una carpeta específica.
Thank you, I have put to work sprites of PIXI in my game but....I have another problem......
some sprites of PIXI give this error (I use GIEPY) SpawnSprite.asm failed" !SprSize not found and it doesn't allow me to place the sprite in my game: (... (this passes with the sprites of snifit,yi bulletbill and other).

as I can repair this? help me once but: (

I also have problems with the sprites of TRASM (Old Sprite Tool Format)
when I install the classic nipper_yi.cfg or the bullet_bro.cfg appears this "Line XXXX Branch out of range" and when I go to it lines her and I fix it (it is Usually a BPL LABELXXX) but when I remove the BPL the sprite it is strange or it doesn't work well or I change him the name of the BPL (Example BPL LABEL 16 to LABEL "another word or I number that it is not 16") AND..... Crash the level:)

Old to asar sprites works good:)

and with the old dynamic sprites (as the old sprites of yoshi island) they give error with the files.bin (and the error already mentioned)...

I have many old sprites that TRASM uses (as the Bowser of SMB3 or the JapSpritePacks and the old mikey sprites like kaboomba,yi goomba etc) that are good and that wanted to use in my hack.

Friends please help me I want to solve this.... I have their help!!!

PD: forgive my bad English.

PD2: because these new programs cause so many problems?, the old Sprite Tool didn't cause them, you that this new generation works but optimized but go! xD.
The !SprSize define, along with other PIXI defines, were missing in the first version of GIEPY. This was fixed long ago - you should use the latest version, 1.0.2. You should also make sure you've enabled PIXI compatibility mode.

I don't know what could be happening with the TRASM sprites. It's probably best to run them through Trashkas and insert them as Asar sprites. TRASM is a notoriously buggy assembler and while I don't want to point the finger solely at it, it might very well be the culprit. Removing or changing branching instructions will only break things further - you're changing the sprite's logic, of course it'll behave weirdly. You generally shouldn't touch code you don't understand.

SpriteTool was undeniably a stable tool but it was unmaintained and limited, especially when SA-1 became popular. The previous ASM team leader, LX5, made the decision to switch to PIXI. At the time, it definitely was a good decision but it backfired due to PIXI's bugginess. By the time I took over, most of the sprites had been converted to PIXI and there wasn't really a way to just go back. GIEPY is maintained, clean, fast, more user-friendly (especially when the tutorials for it are made) and, apart from the small oversights which are quickly fixed (see the first paragraph), quite stable.
Well, you're right, Trasm is quite defective (I used to know about ASM before but this new generation helped me forget everything faster: P) and well I'll see what I can do, is that compatibility mode active? and paste the routine folder to the Gipey directory and put them in the Pixi folder, is that really serious?

and why gipey not are present un the tools section?

I where found a custom sprites tutorial? Tengo ganas de hacer custom sprites
Originally posted by Terios
and why gipey not are present un the tools section?

The reason GIEPY isn't uploaded to the tools yet is because we first want to fixing potential bugs but also standardise shared routines.
Were the issues with PIXI you were talking about causing the game to lock and the background of the title screen to go black? Even with a clean ROM and a built-in sprite?
well ... with this new version of GIPEY some sprites work but others do not ... example the venus plants, when the plant sees to the left it will shoot to the left and vice versa because here the plant sees to the right and shoots to the left ... and the YI-Cannon I install it and for surprise it does not shoot the cannon, and the giant koopas are inserted badly and I crush them and they become strange things, I mean most of the common custom sprites do not work with these " Novelties "programs and my rom is a clean rom.

How can i fix this? I want those sprites to work well.
I wait for your help!

and ... is it advisable to use sprite tool? (after all I will not use SA-1 in my rom)
Originally posted by Terios
example the venus plants, when the plant sees to the left it will shoot to the left and vice versa because here the plant sees to the right and shoots to the left

This is because the sprite uses a rather dodgy way of working around a PIXI bug. You see, PIXI swaps the defines for the X and Y speeds of extended sprites, so the venus plants store the X speed to the fireball's Y speed (which is actually the X speed in PIXI) and vice-versa. GIEPY gets the defines right, which ends up breaking this workaround. To fix it, open piranha_venus_all.asm; change line 688 to STA !extended_x_speed,y and line 692 to STA !extended_y_speed,y.

Originally posted by Terios
the YI-Cannon I install it and for surprise it does not shoot the cannon

This is because of the change to sprite spawning in GIEPY. In SpawnSprite.asm, move line 41 to 37. The fork of GIEPY I released for C3 includes a compatibility layer for such old code. I wouldn't recommend using it yet because only the ASM code is changed and that causes problems when force re-installing the system.

Originally posted by Terios
the giant koopas are inserted badly and I crush them and they become strange things

It appears the Giant Koopas rely on an obscure PIXI feature which GIEPY's PIXI compatible mode does not include. This is also fixed in my C3 fork of GIEPY.

Originally posted by Terios
is it advisable to use sprite tool?

Almost none of the sprites in the section work with Romi's SpriteTool; you'd have to either use the old sprite archive or manually remove the shared subroutines and SA-1 defines. For now, the best option is to stick to PIXI 1.2 with the -npl flag unless you want to keep using GIEPY. If you do use GIEPY, it's best to use my fork, but do keep in mind that it might cause problems if you force re-install the system patch.