EDuke32 on Wii

3 Pages
←
1
2
3
→

You cannot start a new topic
You cannot reply to this topic

EDuke32 on Wii

NUKEMDAVE

#31 Posted 22 May 2012 - 10:35 PM

The max screen resolution should be 720 X 480. That's the max screen resolution the Wii puts out. Unless you want to add some wide resolutions that'll leave black boxes on the top and bottom of the screen.

I happen to be using RGB cables with my Wii, which brings it from 480i to 480p. It looks good!

Edit:

I made this for fun. It's not up to me whether the name should be changed or not, but I think having "Wii" in the name would be better.

This post has been edited by NUKEMDAVE: 22 May 2012 - 11:35 PM

MusicallyInspired

The Sarien Encounter

#32 Posted 23 May 2012 - 04:07 AM

How realistic is having Mapster32 on the Wii? It can support a keyboard and mouse, after all.

Micky C

Honored Donor

#33 Posted 23 May 2012 - 04:37 AM

Aww yeah! Let's get all our mates over, chill out on the couch, invite some girls over and have 3 quick rounds of mapping on the big screen with surround sound and sub woofers

This post has been edited by Micky C: 23 May 2012 - 04:38 AM

High Treason

#34 Posted 23 May 2012 - 04:43 AM

I don't own a Wii, but congrats on the port anyway.

As for the resolution, I might be wrong, but I would assume PAL Wii's output 720x576, so you might want to leave that as a resolution if it is available in the options.

Hendricks266

Weaponized Autism

#35 Posted 23 May 2012 - 07:43 AM

MusicallyInspired, on 23 May 2012 - 04:07 AM, said:

How realistic is having Mapster32 on the Wii? It can support a keyboard and mouse, after all.

The Mapster32 executable built for me when I specifically tried it, but I disabled it from building when PLATFORM=WII because it would be useless and would run into the same control problems as the actual game.

If you really want it, follow the build instructions on the wiki but run:

wiibuild.bat mapster32.elf

NUKEMDAVE

#36 Posted 23 May 2012 - 05:29 PM

High Treason, on 23 May 2012 - 04:43 AM, said:

As for the resolution, I might be wrong, but I would assume PAL Wii's output 720x576, so you might want to leave that as a resolution if it is available in the options.

Well, 720 X 480 is what I'm getting with NTSC. I guess it should have both 720 X 480 and 720 X 576.

Video:

Custom "AV Multi Out" port supporting composite video, YPBPR component video, S-Video (NTSC consoles only) and RGB SCART (PAL consoles only)

480p (PAL/NTSC), 480i (PAL/NTSC) or 576i (PAL/SECAM), standard 4:3 and 16:9 anamorphic widescreen

http://en.wikipedia.org/wiki/Wii

uh . . . .

#37 Posted 23 May 2012 - 06:37 PM

I'll definitely be downloading when the controls work better, haven't tried it but I'll take everyone's word for it. Don't have a USB keyboard or mouse at the moment.

Hendricks266

Weaponized Autism

#38 Posted 23 May 2012 - 07:27 PM

NUKEMDAVE, on 22 May 2012 - 10:35 PM, said:

I made this for fun. It's not up to me whether the name should be changed or not, but I think having "Wii" in the name would be better.

Attachment

EDuke32OrWiiDuke32.jpg

"Wii" is in the name: "EDuke32 Wii".

A better source exists for the icon image than that thing. In the EDuke32 source, you can find "EDuke32_logo_21_large_opaque.psd". This is the source vector image created in Photoshop.

What is the font? Daidoh?

NUKEMDAVE

#39 Posted 23 May 2012 - 09:33 PM

Hendricks266, on 23 May 2012 - 07:27 PM, said:

Yeah, but that's longer. WiiDuke32 is shorter and I think it would be cooler, but that's just me. Yep, Daidoh.

Player Lin

#40 Posted 24 May 2012 - 07:18 AM

WiiDuke32 sounds like nothing to do with eduke32, cool? You gotta kidding me.

At least if called Wii-eduke32 or edukeWii, it would make sense.

This post has been edited by Player Lin: 24 May 2012 - 07:22 AM

Jinroh

#41 Posted 24 May 2012 - 07:28 AM

I think WiiDuke32 is actually pretty clever. xD

TerminX

el fundador

#42 Posted 24 May 2012 - 07:41 AM

Please don't call it "WiiDuke32." I don't know if some of you came up with that independently or what, but when I said we should call it that on IRC about a week ago I was 100% kidding. "WiiDuke32" makes it sound like it's some special version or even a different program entirely, and that's simply not the case... it is merely EDuke32 compiled for the Wii. Similarly, the Android port will not be known as "AnDuke32," the Linux version is not "LinDuke32" and ports to BSD are not "BSDuke32."

The Commander

I used to be a Brown Fuzzy Fruit, but I've changed bro...

#43 Posted 24 May 2012 - 09:20 AM

It would also just end up causing more confusion for the n00bs that are not in the "know of ports"

MusicallyInspired

The Sarien Encounter

#44 Posted 24 May 2012 - 04:21 PM

Many homebrew applications utilize the "Wii" name-in-name thing and it was kind of cool....until multiple versions started coming out that all had different names. It is clever, but just keep it EDuke32 Wii.

Jimmy

Let's go Brandon!

#45 Posted 24 May 2012 - 07:38 PM

Cody, while I think you're right, n00bs will find any reason to get confused.

nightwishfan1

#46 Posted 25 May 2012 - 09:16 AM

Hendricks. I went and recreated the crash I experienced, and I have the stack dump data from it. Hopefully that can help you track down the exact issue, and issues like it since it's level related. Also this is the info most wii homebrew programmers use to track down issues with their apps. This crash occurred at level 2 of episode 1 in the back portion of the magazine shop, where it's dark. Anyways the stack dump info is below.

Stack dump read out from the Wii when EDuke crashed: 800c3fc0 --> 800c35c4 --> 800139f4 --> 8001c0d0 --> 800f8500 --> 80171c3c --> 80004348 --> 801a5a0c --801a59bc

As a note to everyone else....You all should also record any crashes that occurr. Specifically the stack dump portion if it's presented on screen when the crash occurrs. That portion is usually most relevant to what prompted the app to crash in the first place, and it will only help make the app better as Hendricks will be able to identify the crashes more easily instead of looking blindly for them. Or even attempting to recreate them, and they dont occurr for him.

Also a question. You mention Classic Controller support being added in the next release...Will this include Gamecube controller support? To me that would be pretty cool since most of the older Wiis that people own support those controllers. Thanks.

This post has been edited by nightwishfan1: 25 May 2012 - 09:33 AM

Hendricks266

Weaponized Autism

#47 Posted 25 May 2012 - 10:27 AM

nightwishfan1, on 25 May 2012 - 09:16 AM, said:

Stack dump read out from the Wii when EDuke crashed: 800c3fc0 --> 800c35c4 --> 800139f4 --> 8001c0d0 --> 800f8500 --> 80171c3c --> 80004348 --> 801a5a0c --801a59bc

As a note to everyone else....You all should also record any crashes that occurr. Specifically the stack dump portion if it's presented on screen when the crash occurrs. That portion is usually most relevant to what prompted the app to crash in the first place, and it will only help make the app better as Hendricks will be able to identify the crashes more easily instead of looking blindly for them. Or even attempting to recreate them, and they dont occurr for him.

I recall reading an article somewhere on Wii Homebrew forums or blogs explaining how to work with these, but I can't find it now.

I was able to pull an image of a stack dump out of this video and it looks like it matches your stack dump, which is great news meaning there is only one bug at work.

Also, I have experienced these crashes myself.

Posted Image

nightwishfan1, on 25 May 2012 - 09:16 AM, said:

Also a question. You mention Classic Controller support being added in the next release...Will this include Gamecube controller support? To me that would be pretty cool since most of the older Wiis that people own support those controllers. Thanks.

Absolutely. GameCube controllers have a notable objective advantage over Classic Controllers: their analog sticks have 8-bit precision rather than 6-bit on the CC. (IIRC the only downside is that they lack a ZL button.) Also, I have four GC controllers already, while I had to / would have to (birthday coming up lol) buy a CC controller to develop with it.

Plagman

Former VP of Media Operations

#48 Posted 25 May 2012 - 10:41 AM

The Wii toolchain must come with a set of binutils, that you can use to figure out where these addresses are in the binary code (objdump).

Hendricks266

Weaponized Autism

#49 Posted 25 May 2012 - 11:08 AM

florscan/getpalookup/hline --> florscan --> clamp --> G_DoCheats (?) --> buildkeytranslationtable --> main --> _crtmain exit --> __lwp_thread_handler --> .text __lwp_thread_handler

EDIT: This does not look helpful. I need to find that article.

EDIT: Can we have some users test if you bind a key to LOOK_LEFT or LOOK_RIGHT (not TURN_) and see if that crashes the game due to the screen tilting?

This post has been edited by Hendricks266: 25 May 2012 - 11:15 AM

nightwishfan1

#50 Posted 25 May 2012 - 08:46 PM

Hendricks266, on 25 May 2012 - 10:27 AM, said:

I recall reading an article somewhere on Wii Homebrew forums or blogs explaining how to work with these, but I can't find it now.

I'm not sure myself how to interpret these crash dump codes to correct them, but I would test newer beta versions of already established homebrew apps that I was particularly interested in, and the developers working on those would tell me to record that specific section of the crash, or somehow document the error if the stack dump portion wasnt present when the app would crash. This would usually be difficult, cause you cant always anticipate the errors happening consistently, or only I would experience the error while the developer couldnt recreate it. Luckily this error in WiiDuke seems consistent for everyone using it. Only thing I can suggest would be to probably contact tueidj at the Wiibrew forums for assistance. Him or any other member who has experience developing Wii homebrew. If I knew anything about coding I'd help, but I dont.

Hendricks266

Weaponized Autism

#51 Posted 26 May 2012 - 04:07 PM

Work is progressing on the to-do list.

Since I am developing away from my Wii, I need beta testers who can test quickly and who can give me IM contacts. See my contact page. Send me an email.

nightwishfan1

#52 Posted 26 May 2012 - 04:47 PM

^^I'll volunteer to test out whatever betas you make. I'm mostly limited to mornings during weekdays however since I work second shift. Weekends I have off from work, and can be a bit more productive with the testing. Only thing I'd need to know is where you'd upload these betas to be able to test them. And when I do test them I'd need to have some idea of what you're looking at specifically being affected with a particular beta build. I also happen to have your AIM screen name that you got listed in your profile, but if you prefer e-mail contact than that's fine.

NUKEMDAVE

#53 Posted 26 May 2012 - 08:55 PM

I'm already beta testing for it and even helped a little in another way. Some progress has been made. It's almost playable with the Wii remote and nunchuk.

NF64

Touched by the Banhammer

#54 Posted 27 May 2012 - 01:06 AM

XICO2KX, on 30 April 2012 - 12:14 PM, said:

If someone wants to pick up the development, tueidj has already a working port of EDuke32 running on the Wii!

You can watch it in action here and check the details here:

http://wiibrew.org/w...r:Tueidj/Duke3D

NUKEMDAVE, on 22 May 2012 - 12:00 AM, said:

I made a video before I got the music working.

http://www.youtube.c...player_embedded

I prefer calling it WiiDuke32.

Well I do have to say this is very impressive and brought a small heart warming feeling.
Congratz to tueidj.

Hendricks266

Weaponized Autism

#55 Posted 31 May 2012 - 09:26 PM

I'm doing work to improve the controls and for the past week I have been working through the menu code tracking down little problems that need to be fixed but have solutions that take lots of digging. Sometimes trial and error doesn't even work. I'm tearing my hair out. As far as I'm concerned, the menu code is this: http://www.theonion....t-doesnt,14309/

XICO2KX

#56 Posted 02 June 2012 - 06:03 AM

Hendricks266, on 31 May 2012 - 09:26 PM, said:

I don't think I can help you...

But tueidj has lots of experience with all that Wii coding/hacking stuff!

Maybe you should contact him and ask him for some hints!

This post has been edited by XICO2KX: 02 June 2012 - 06:05 AM

Hendricks266

Weaponized Autism

#57 Posted 02 June 2012 - 10:39 AM

I fixed most of the stuff. It had nothing to do with the Wii specifically anyway so there was no reason to ask tueidj. If there was a reason, I would (and have in the past) contacted him.