DualStick + CDZ Button DC Controls

[Roareye]

https://segaxtreme.net/threads/about-ip-bin.6229/

Second post in this topic states that hex editing of controls is possible. While the initial post asks about Saturn, this guy talks about Dreamcast instead.

There is a lot of stuff in IP.BIN - the game name, publisher, etc., name of the first file to load and execute (usually 1ST_READ.BIN), whether the game is a SegaOS (Katana) one or a WinCE one, whether VGA/RGB are supported, what kinds of input the game accepts - there are separate flags for each single button and direction on the normal controller, as well as lightguns, mice, whatnot - what regions the game will work in.... TONS of stuff! And there's even executable code inside IP.BIN, usually of the sort that finds and loads the specified file.

If it wasn't possible, I'm sure megavolt85 (someone who has the ability to, whether it would interest him or not is another matter) or someone else would have said so by now. In fact it's not a case of if it is possible, merely a case of whether someone would care to do it. Roel has mentioned he would be interested in the controls, but currently there's no controller capable of doing it. If made available, there's plenty of demand.

I can agree, though, it would require someone with code knowledge to pull off. Decompiling each game, finding the code to alter and what to alter it to, then releasing the modded GDI/CDI. That's why I'm asking here for us to work together to build the response.

[Motoracer5]

Spent a lot of time with the Intrepid Izzy demo on my Dreamcast! Will definitely pick it up once it hits the PS4 store. Would be awesome to see a twin stick shooter on the Dreamcast with that level of sprite and animation quality

[Roel]

I could loan you a Brook DS4 to dreamcast adapter. Works with a 8bitdo M30 wired as well, but it dosen't support Xbox or Switch pads. Should be fine for letting you see where code needs to be changed to let the Team Senile games work with the Brook adapter. PM me if you are interested

That is a wonderful offer, but from the previous posts I understood that the Brook adapter doesn't support the second stick anyway? Anyway I'll PM you.

https://segaxtreme.net/threads/about-ip-bin.6229/

Second post in this topic states that hex editing of controls is possible. While the initial post asks about Saturn, this guy talks about Dreamcast instead.

There is a lot of stuff in IP.BIN - the game name, publisher, etc., name of the first file to load and execute (usually 1ST_READ.BIN), whether the game is a SegaOS (Katana) one or a WinCE one, whether VGA/RGB are supported, what kinds of input the game accepts - there are separate flags for each single button and direction on the normal controller, as well as lightguns, mice, whatnot - what regions the game will work in.... TONS of stuff! And there's even executable code inside IP.BIN, usually of the sort that finds and loads the specified file.

If it wasn't possible, I'm sure megavolt85 (someone who has the ability to, whether it would interest him or not is another matter) or someone else would have said so by now. In fact it's not a case of if it is possible, merely a case of whether someone would care to do it. Roel has mentioned he would be interested in the controls, but currently there's no controller capable of doing it. If made available, there's plenty of demand.

I can agree, though, it would require someone with code knowledge to pull off. Decompiling each game, finding the code to alter and what to alter it to, then releasing the modded GDI/CDI. That's why I'm asking here for us to work together to build the response.

I don't think that modifying IP.BIN will get you anywhere. It is certainly true that it contains information about the game, but AFAIK that data is purely descriptive. Hex editing IP.BIN is like writing "supports 2 analog sticks" on the packaging. Just because you say so doesn't make it true.

The actual game code is in 1ST_READ.BIN. That's where the inputs are handled and the game decides what to do with them.

[Motoracer5]

That is a wonderful offer, but from the previous posts I understood that the Brook adapter doesn't support the second stick anyway? Anyway I'll PM you

It dosen't, but Intrepid Izzy and RRRR do not work with the adapter. Both games would be great to play with a variety of arcade sticks and controllers.

Twin stick shooter would have to be on another platform. Unless you produce megavolt85's board and bundle it with the game More realistically a 8way like Xeno Crisis plays quite well with the Brook mapping face buttons to right stick on Dreamcast. I was honestly blown away at the quality 2d you got running on the old Dreamcast. Would love to see that talent and style in a shmup/twin stick!!

[Roel]

It dosen't, but Intrepid Izzy and RRRR do not work with the adapter. Both games would be great to play with a variety of arcade sticks and controllers.

Oh! I was unaware of that. That's actually a problem with the adapter itself (if it emulated the original controller perfectly this issue wouldn't exist), but I would like to see what I can do to fix it. Thanks for pointing it out!

[Roareye]

I don't think that modifying IP.BIN will get you anywhere. It is certainly true that it contains information about the game, but AFAIK that data is purely descriptive. Hex editing IP.BIN is like writing "supports 2 analog sticks" on the packaging. Just because you say so doesn't make it true.

The actual game code is in 1ST_READ.BIN. That's where the inputs are handled and the game decides what to do with them.

Ah, thanks for correcting me on the file (IP.BIN was stated in the post I linked, but I know you know what you're talking about for sure).

[megavolt85]

That is a wonderful offer, but from the previous posts I understood that the Brook adapter doesn't support the second stick anyway? Anyway I'll PM you.

small example

Code: Select all

	maple_device_t *controller;
	cont_state_t *cont_stat;
	
	controller = maple_enum_dev(0, 0);
	
	if (!controller)
	{
		/* controller not connected */
		return -1;
	}
	
	cont_stat = (cont_state_t *) maple_dev_status(controller);
	
	if (!cont_stat)
	{
		/* Can't read controller */
		return -1;
	}
	
	if (controller->info.function_data[0] & CONT_CAPABILITY_ANALOG2_X)
	{
		/* controller have second analog X axis */
		
		stick2X = cont_stat->joy2x;
	}
	
	if (controller->info.function_data[0] & CONT_CAPABILITY_ANALOG2_Y)
	{
		/* controller have second analog Y axis */
		
		stick2Y = cont_stat->joy2y;
	}

[Roel]

That is a wonderful offer, but from the previous posts I understood that the Brook adapter doesn't support the second stick anyway? Anyway I'll PM you.

small example

Code: Select all

	maple_device_t *controller;
	cont_state_t *cont_stat;
	
	controller = maple_enum_dev(0, 0);
	
	if (!controller)
	{
		/* controller not connected */
		return -1;
	}
	
	cont_stat = (cont_state_t *) maple_dev_status(controller);
	
	if (!cont_stat)
	{
		/* Can't read controller */
		return -1;
	}
	
	if (controller->info.function_data[0] & CONT_CAPABILITY_ANALOG2_X)
	{
		/* controller have second analog X axis */
		
		stick2X = cont_stat->joy2x;
	}
	
	if (controller->info.function_data[0] & CONT_CAPABILITY_ANALOG2_Y)
	{
		/* controller have second analog Y axis */
		
		stick2Y = cont_stat->joy2y;
	}

Thanks megavolt85, but sadly this is no use to me at all, because:
1. I assume this code is for KOS, which I do not use.
2. I already know how to check if a second stick is present and how to read its data. The only problem, as stated before, is that I can't test it for lack of hardware.
3. The code you posted does nothing when combined with the Brook adapter. Until someone updates its firmware, the last 2 if-statements will always evaluate to FALSE.

-edit-
Of course if I had a working STM32F103C8T6-based adapter it might be a different story, but I don't, and I'm not good enough with soldering and such to make one.

-edit 2-
Also I don't have nearly enough time to tinker with experimental electronics before the game's release anyway.

[Roareye]

Should I send the template email as is?
Is it clear enough to get the message across?

Hoping they will understand venough to make the firmware changes (otherwise it'll be down to us to modify the firmware, which would be a pain in the arse).

[Anthony817]

I say send it as it. Maybe they will understand it better than the first message.