Last edited by niuus,
Well, i don't know what you're trying to reach by using arguments at all.
Theoretically this would be part of the code. But they wouldn't reach anywhere because I turned this stuff off. It simply wouldn't make any sense at all i think, as everything is being assigned to the game through my loader (main IWAD file location etc.).
Last edited by nitr8,
No. You explained nothing in detail.I kindly asked from you if I could turn your criticism into a constructive dialogue, but it seems you were pissed off for some unknown reason. What a shitty attitude, man!
- You find the analogue controls to be wonky? Yes they are, but hey, games like Duke, Wolf, and even ROTT were never intended to be played with analogue controls, to start with. It's not real 3D. But good luck if you want to try it.
- No Wii-U/USB pad support? True, but not a valid reason to say that something is FAR from perfect, in my book.
- Lastly, Flashback, Another World and Commander Keen ep 4-5-6 are all perfectly playable without doing anything complicated, using the pack in my Dosbox Thread. You just have to copy two files and... BAM! Full speed and mapped controls. T W O F I L E S
Sorry everyone for this big Off Topic, this will be my last reply on this matter
Then stop ASKING again and again about the same thing, and give up on the DOSBox agenda. You like it, love it to death?
Fine! I commend your spirit but i am not obligated to use your packs. I already said i don't want to use them and i don't want to use DOSBox on a Wii (no point for me). Having to overexplain when i already gave a perfectly concise and polite explanation, only to be refuted again with "but why port it when DOSBox somethingsomething??" quickly became a nuisance since i already told you my valid reasons, i was beginning to think you were kinda trolling. Now can we move on and could you stop derailing the thread?
NOW ON TOPIC:
WIIROTT R3 has been working very fine, though it will surely take me a while to end the game, as from what i've seen in reviews, the game is really huge, more so than Doom, i think.
with arg support wiiflow could send the path of a iwad or rtl file as an arg when it launches your wiirott app and your app would see the arg an just skip the loader and go straight to launching the iwad or rtl file as if the user had selected it.
Sorry, but i still don't get it...
Just WHY would you run Wiiflow all the time instead of running the HBC to load your stuff...?
people like using wiiflow as a frontend. via its plugin system they can display the games via cover images and game snapshots and even game info. easily click play and have the emulator or game engine start and play the game they selected. and it certainly looks much nicer than a simple text gui loader.
@nitr8 , many of us really do enjoy using WiiFlow as our primary loader. You would certainly make a lot of WiiFlow users very happy by including support for arguments in your Wii homebrew ports.
To answer your question, I personally prefer using WiiFlow simply because I like having everything all in one place, rather than booting different dols through the HBC. Plus WiiFlow just looks really nice and gives a nice sense of physical tangibility to your digital collection of games and programs.
There's just a certain magic to picking up a game's box and being able to observe its artwork, reading the back for details, then finally open it and play it. In modern times this has been largely lost; digital games have succumbed to being a flat panel of artwork or a string of lifeless text you can click on to start playing. WiiFlow recaptures much of that old magic feeling of picking up a game box and absorbing its essence before playing it.
This is why I would love to be able to play your excellent game ports in WiiFlow, @nitr8 . They are great classic games and would be perfect for WiiFlow.
To answer your question, I personally prefer using WiiFlow simply because I like having everything all in one place, rather than booting different dols through the HBC. Plus WiiFlow just looks really nice and gives a nice sense of physical tangibility to your digital collection of games and programs.
There's just a certain magic to picking up a game's box and being able to observe its artwork, reading the back for details, then finally open it and play it. In modern times this has been largely lost; digital games have succumbed to being a flat panel of artwork or a string of lifeless text you can click on to start playing. WiiFlow recaptures much of that old magic feeling of picking up a game box and absorbing its essence before playing it.
This is why I would love to be able to play your excellent game ports in WiiFlow, @nitr8 . They are great classic games and would be perfect for WiiFlow.
Last edited by Hakaisha,
First, make an actually USABLE working version of WiiFlow first as this was my first doubt why i should include args:
I almost tried pulling a completely fresh v5.4.0 of WiiFlow from GitHub, started it, it took like 25 seconds to go from the logo into the main menu and once being there, if you press "Y" on a Classic Controller, WiiFlow immediately crashes with a DSI exception. So much for "expecting other people to include stuff in their apps so my own bugged stuff can load those apps correctly"...
I'm definitely not happy with that.
If you've fixed that, I'll think about it. otherwisely: NO. Sorry, but i have to decline that for now.
EDIT: Same thing for pressing "1" or "2" on a simple Wiimote at the very same situation.
EDIT2:
Well, i kinda drop even thinking about including args.
Just tried to load one of my games through WiiFlow "apps menu" and it just gave me a black screen.
Last edited by nitr8,
First, make an actually USABLE working version of WiiFlow first as this was my first doubt why i should include args:
I almost tried pulling a completely fresh v5.4.0 of WiiFlow from GitHub, started it, it took like 25 seconds to go from the logo into the main menu and once being there, if you press "Y" on a Classic Controller, WiiFlow immediately crashes with a DSI exception. So much for "expecting other people to include stuff in their apps so my own bugged stuff can load those apps correctly"...
I'm definitely not happy with that.
If you've fixed that, I'll think about it. otherwisely: NO. Sorry, but i have to decline that for now.
EDIT: Same thing for pressing "1" or "2" on a simple Wiimote at the very same situation.
EDIT2:
Well, i kinda drop even thinking about including args.
Just tried to load one of my games through WiiFlow "apps menu" and it just gave me a black screen.
that's very odd. '1' and '2' and 'y' work perfectly fine for me. and i've never had any one else mention it. i even removed coverflow default ini from the coverflows folder and it still works.
what game did you try? did you try any other apps? when you installed wiiflow 5.4.0 did you install the bins folder and its contents? where is the game installed sd or usb?
I didn't even run ANY game. I just started WiiFlow and after getting into the main menu, just hit those buttons -> CRASH!
WII-ROTT updated!
Link within FIRST post in this thread.
For WII-ROTT:
- FIXED FULLSCREEN FLAW (now at least renders fullscreen for PAL inside the menu and game itself as the game was previously overscanning PAL devices)*
*: ROTT's code is somewhat highly modified and it almost was when i pulled the fresh SDL source from Icculus' website. I had major troubles getting the fullscreen fix done and you need to check if it works for NTSC the proper way as i have no real chance to test it on a real NTSC console. Though, i DO have a Wii with NTSC output but it was only modified using AnyRegionChancer. My screen is a PAL one, while it recognizes NTSC but it's not quite the same as living within a real NTSC region...
Link within FIRST post in this thread.
For WII-ROTT:
- FIXED FULLSCREEN FLAW (now at least renders fullscreen for PAL inside the menu and game itself as the game was previously overscanning PAL devices)*
*: ROTT's code is somewhat highly modified and it almost was when i pulled the fresh SDL source from Icculus' website. I had major troubles getting the fullscreen fix done and you need to check if it works for NTSC the proper way as i have no real chance to test it on a real NTSC console. Though, i DO have a Wii with NTSC output but it was only modified using AnyRegionChancer. My screen is a PAL one, while it recognizes NTSC but it's not quite the same as living within a real NTSC region...
Last edited by nitr8,
SOLVED - it appears some 3rd party wii classic controllers have issues being recognized by some libraries. A standard OEM classic controller works fine with WiiROTT.
Post automatically merged:
SOLVED - it appears that some 3rd party classic wii controllers do not properly set a value that's recognized by some libraries. I swapped in a classic wii OEM controller and it works fine!!!
Similar threads
- No one is chatting at the moment.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
RedColoredStars:
There is an actual trailer with footage too. lol. Going to watch it tonight. Grabbed it from... a place. -
-
@
SylverReZ:
@Psionic Roshambo, JonTron's back yet again until he disappears into the void for another 6 or so months.+1 -
-
-
