- Trial Member: Trial Members
- Active Posts:
- 42 (0.04 per day)
- Most Active In:
- Engineering & Reverse Engineering (8 posts)
- 08-February 12
- Profile Views:
- Last Active:
- Today, 02:39 PM
- 17 years old
- October 14, 1997
- National Flag:
Posts I've Made
18 October 2014 - 02:56 AMEdit: Never mind, I misread. BTW, wrote some new stuff to the post.
14 October 2014 - 08:08 PMUpdate: beta 0.1.1
(* = fixed bug, + = added feature, - = removed feature)
+ ability to choose palette line offset
+ commandline support
+ You can now select tile from the plane using O instead of only Middle Click
* using Numpad on text fields will type "Numpad #" instead of "#"
* pressing Numpad 9 or Num 9 will not work
* you cant use colon or semicolon to write said characters
* if you have less palettes than what plane uses, it will crash (Warning: now it just reads from existing lines!)
* you are able to edit multiple textfields at once
* compression format "Uncompressed" fails to automatically exit its command prompt and must be exited manually.
* The editor itself may not be in a filepath that contains any whitespace characters ( ) due to a bug with commandline. However, edited files can be in any kind of filepath.
14 October 2014 - 01:17 PMThank you! And that reminds me I forgot to add Comper compression as well.
14 October 2014 - 02:58 AMEdit2: So, I cannot get the "Open Project" button to do anything. I tried to hand make a project file, since the built-in setup for it glitches so text overlaps. So far I haven't gotten anything to load. =/
I forgot to specify, that the project files must be saved to "projects" in the programs launch path. woopsie. But the Open project button will only work if there is at least 1 project in said folder. I will also include example project download. (You must change to the correct path for your disassembly in order to make it work). Also, you can try to fix the overlapping by maximizing the window before going to the editor.
Also, Kazblox, mind showing screenshot and the project file contents?
08 October 2014 - 09:37 AMJust looking at the code, I found few possible causes for it not to work:
- Your object will be created at either x $10, or x -$10, and y 0. You never copy X and Y positions from Sonic's RAM in above code.
- Most of the time, when running the object, a1 will not point to Art_Lazerart, with the exception of initializing frame, because you define it at Obj10_Cont, which isn't accessed if routine counter is 2 or above.
- It seems you are trying to do some kind of Dynamic art loading method in the routine as well, but it doesnt seem you actually ever load the art