| |||
Views: 88,516,661 |
Main | FAQ | Uploader | IRC chat | Radio | Memberlist | Active users | Latest posts | Calendar | Stats | Online users | Search | 05-03-24 12:04 AM |
|
Guest: Register | Login |
Main - Posts by Stifu |
Stifu |
| ||
Cobrat Level: 56 Posts: 321/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
Hi,
1. This will be in the next version. 2. No idea, first time I hear about this. If you send me your ROM, I can have a look. Or better yet: steps to reproduce the problem from a clean ROM. As far as I know, you should be able to 128 AI elements per track. But you can still try deleting some just to make sure... You're using Epic Edit 1.6, right? Is your ROM Jap, US or Euro? There were track corruption issues in 1.5, for non-US ROMs, that's the last track corruption bug I've come across. 3. Not yet, maybe later. But you can still easily do it using a hex editor. |
Stifu |
| ||
Cobrat Level: 56 Posts: 322/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
It's probably the track map itself that the editor can't properly compress. You could confirm this by making a copy of your game, exporting the problematic track map, and importing it on another track. If that other track also appears as corrupt, then bingo. In which case you could send me the track map file so I can have a look. |
Stifu |
| ||
Cobrat Level: 56 Posts: 323/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
The first battle course is slightly different from the others, as it originally as different AI data, and different starting positions (which can't be edited yet through Epic Edit, for the record), but this shouldn't be a problem, and shouldn't cause what you see... Unless there are other differences I'm unaware of.
I take it you didn't modify your ROM manually, and simply used Epic Edit, is that right? I just tried importing Battle Course 2 then 3 over Battle Course 1, and the track wasn't corrupt, all was fine. Maybe you didn't start your hack from a clean / valid ROM? Just making sure, as that was the case with Raccoon Sam at the beggining of this thread... |
Stifu |
| ||
Cobrat Level: 56 Posts: 324/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
Posted by Gamma1227 At the moment, the only way is through the tileset, select and use the 4 tiles that make up an item block (at the bottom of the tileset). Once you've done it once, you hold the right mouse button to select the item block you created, to copy / paste it elsewhere. In the next version, you'll be able to add item blocks (and other stuff) the same way the original are done: on another layer. The difference it makes, when playing, is whether they show up in Time Trial. If you add them as regular tiles, they will. |
Stifu |
| ||
Cobrat Level: 56 Posts: 325/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
To make these images work, remove the "?attredirects=0" part at the end of the URL.
|
Stifu |
| ||
Cobrat Level: 56 Posts: 326/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
Posted by gridatttack I've thought about this, yeah. The limit is 42 overlay tiles per track (I didn't check whether this limit can be lifted). In the original SMK ROM, the biggest overlay tile pattern is 5x5 tiles (for coins). However, it's possible to create your own overlay tile patterns that would be bigger than that. The next version of Epic Edit will let you edit overlay tiles, but not create your own patterns. Maybe later. |
Stifu |
| ||
Cobrat Level: 56 Posts: 327/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
What is the editor written in, out of curiosity? |
Stifu |
| ||
Cobrat Level: 56 Posts: 328/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
Epic Edit 1.9 is out. Yay.
Announcement: http://stifu.free.fr/en/news.php |
Stifu |
| ||
Cobrat Level: 56 Posts: 329/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
Indeed, there was a nasty regression (which also affects the theme combo box).
I just uploaded v1.9.1, which fixes this. https://epicedit.stifu.fr/download/EpicEdit_1.9.1.zip I'll update the site soon. |
Stifu |
| ||
Cobrat Level: 56 Posts: 330/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
I take it you already set the AI element speed to the max where needed, right? If so, I'm not sure what else you can do.
By the way, I think the terrain type never affects the CPU speed. I just double checked by adding speed arrows on Mario Circuit 1, and they don't affect the CPU. |
Stifu |
| ||
Cobrat Level: 56 Posts: 331/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
Personally, I simply use an unsafe FastBitmap class (this is a slightly modified version of something I found on the net).
From the outside, you don't need to care about the details (OOP, yay) ; it's like the regular Bitmap class, except you have a Release method to call to unlock the Bitmap. I messed around trying to get a safe but still fast Bitmap class, and got quite good results, but not as good as the unsafe one. |
Stifu |
| ||
Cobrat Level: 56 Posts: 332/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
Simple examples on how to use |
Stifu |
| ||
Cobrat Level: 56 Posts: 333/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
Epic Edit 2.0 is out!
Features MAKE track compatibility. Announcement: http://stifu.free.fr/en/news.php |
Stifu |
| ||
Cobrat Level: 56 Posts: 334/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
Posted by Scatt-Man Among other things: - Battle track starting positions edition - Object type / behavior selection - Ghost Valley pillars edition - Track background edition - Color palette edition - Driver stats edition - Track name edition - Tile type edition - Paint bucket - Undo / redo Not sure I'll do everything. |
Stifu |
| ||
Cobrat Level: 56 Posts: 335/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
Oh. I guess I still need to brush up my English. |
Stifu |
| ||
Cobrat Level: 56 Posts: 336/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
Posted by Trax You mean I just bothered correcting the Epic Edit change log and my site news for nothing? |
Stifu |
| ||
Cobrat Level: 56 Posts: 337/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
It may be more ambiguous than "editing", but it's still not the wrong word from what I understand.
And I think it stands to reason that I'm going to add features after features and keep each of them around, rather than randomly trashing my work by making certain features only available in certain versions. No matter, I'll just say editing from now on. |
Stifu |
| ||
Cobrat Level: 56 Posts: 338/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
The editor works for me on Windows XP, and it also works with Mono.
If this is a simple .NET app, as it seems to be, there's no reason it wouldn't work as long your system isn't fucked up and that the .NET framework is installed. |
Stifu |
| ||
Cobrat Level: 56 Posts: 339/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
Posted by blackhole89 Easy to fix. It's just that IDEs tend to add unnecessary "AutoScale" properties (AutoScaleDimensions, AutoScaleMode) that make sizes vary depending on the OS font size, which tend to cause issues (even on Windows, if you've changed your font settings). Looking at this editor, I can see it indeed sets the AutoScaleDimensions property. Just gotta remove that line. http://www.mono-project.com/FAQ:_Winforms |
Stifu |
| ||
Cobrat Level: 56 Posts: 340/666 EXP: 1362003 Next: 36173 Since: 02-22-07 Last post: 692 days Last view: 314 days |
The FastBitmap class is not a replacement for the DrawImage method. It just makes GetPixel and SetPixel much faster. But once your image is created, you should keep the Bitmap and drop the FastBitmap, and you should still use DrawImage.
Do not use GetPixel or SetPixel for each control repaint, whether with Bitmap or FastBitmap. If you're already caching as much stuff as you can, I think you should just look into clipping, so you don't fully repaint the control when it should only be partially repainted. Edit: I forgot one detail: to optimize performances further, ensure all your Bitmaps use PixelFormat.Format32bppPArgb. |
Main - Posts by Stifu |
© 2005-2023 Acmlm, blackhole89, Xkeeper et al. |
MySQL - queries: 129, rows: 161/161, time: 0.227 seconds. |