THE SonED2 thread

CTRL+Z apparently doesn't disallow deletion of Block 000 (Not Block001, may be the last one you caught before the crash) in the current release. The simpler way to remove all tiles, though, is to delete the tile file, and it will open blank

According to the date of this post, you must be using Demo 6. There are two things that could be going wrong:

1 - If you copied the SonED2 output over Test Zone, you have too few display planes. Test Zone tries to spawn 7, and a standard level would normally have only 3 or 4 (SonED2 outputs 4). Try writing over SIZ, or in the new Demo 7, GHZ

2 - SonED2 outputs tile planes with no scroll properties, because there is nowhere to get them from. You will have to start in editor mode before gameplay begins (press E during the titlecard, or use -warp and -editor, or the launcher's warp and editor options), switch to the background planes (including the blank one) and set them to "relative" type, and set their X and Y scrolling to 0/64. Leave them this way until you're ready to define the actual scroll properties, this is so the game doesn't try to display beyond the plane boundaries. Also, SonED2 outputs in this way-
0 - B Low
1 - A Low
2 - B High
3 - A High
Though, the current init script included with Project Mettrix uses the planes in this way:
0 - B Low (Background)
1 - B High (Secondary Background)
2 - A Low (Foreground)
3 - A High (Superforeground)
Use the editor's Ctrl+C, Ctrl+D, Ctrl+A, and Ctrl+P options to copy A low (plane 1), Delete A low (plane 1), Add a new plane below A High (now at Index 2, creates a new Plane 2), and paste A low to the new plane 2. This will put the planes in the correct order. Or, alternatively, edit the level init script to use the planes in the same order as they are output from SonED2

E02 relies on proper script and data setup, so make sure you know what you're changing and what it will expect to find when you modify anything. The current documentation should still be sufficent as far as that goes

 

It's been brought to my attention that there's an error in SonED v1.02 involving level size and the 1, 2, 3, and 4 keys. This is most likely the cause of the previous error I responded to in this thread, but there was nothing reported to lead me to the possibility of those keys being involved, so I assumed it was a Ctrl+Arrows (harder to mistakenly press) issue with Sonic 2 (whose level size is required by an unmodified Sonic 2 level system to stay at a fixed size)

The keys changed the editor's level layout size settings without correcting the level data aray, in this manner:

1) x--
2) x++
3) y--
4) y++

This meant that you could also correct the mistake, but only if you did it before exiting the editor, and only if you knew how to use them. They weren't meant for inclusion, though. It was just some really old code that I apparently forgot to disable. Ctrl+Arrows is (and was) the proper way to manage level layout size

I've heard that this has caused a few people problems with having accidentally triggered it, so I made a quickfix to prevent you from having to deal with it at all anymore:

SonED2 v1.03

That will have to do for now, since I still have several things to sort out before making a proper update

Sorry for the inconvenience

 

Just out of nowhere? I know you've been using it without problems until now. Did anything at all happen after double-clicking the program icon before the first DirectX error message?

What did you recently change about your computer? Any one thing could end up being important

Newer isn't always better. Did you recently "upgrade" DirectX? Try an older version if you can get the thing to install (I've used "DirectX Eradicator" before, but I've never installed 10).. I don't know about 10's compatibility, and Microsoft couldn't follow a standard to save their lives, even if they set it themselves. SonED2 is compiled with a DX7 SDK, and I'm currently using 9.0c

Is your video card new? If it is, what were you using before?

Are you running a different version of Windows than before?

Were you running any other DirectX programs already when you tried to run SonED2?

What color depth setting are you using? Have you tried others?

...have you tried resetting the computer?

 

That's the problem with your criteria- the stuff you're running is new, and the "diagnostic" program you're running was made by Microsoft themselves and targetted to diagnose only certain issues with the newest version and features, which is all they care about. What I was trying to say was that it's not impossible that they broke backward-compatibility. SonED2 is compiled with the DirectX7 SDK, and even that's only because anything lower wasn't readily available; it doesn't NEED DX7

I really don't have a good idea of what's happening, at the moment. If all you changed was your video card, it must be something about that card's driver. I know from personal experience that it works fine in XP, and you say it was working with DX10 previously.. that's really all it could be. There must be something about the driver or the installation that isn't playing nice with DirectX when DX7 calls are made, or something. Maybe try uninstalling and reinstalling the driver, updating it, downgrading it.. I don't know

I'll try thinking about it, but if messing with the driver doesn't help, I really don't know what to do. It works with so many other things, and the issue here is coming when brand-new video hardware is introduced, and when they build that stuff they barely even care if it works with stuff that was released within the last week or so, anyway, as long as you just keep buying new games, OS, and hardware every-other-day

If anybody else has the same video card and can confirm whether or not they can run SonED2, or E02 (try and run a copy of that and see if it does work for some reason), along with providing OS, DirectX, and other system information, that would be great