Homebrew [Help wanted] DualHexen issues in DSi.

[Nikokaro]

Has anyone ever tried DualHexen (the latest version) on DSi, from SD-slot? You have surely noticed 2 serious flaws:
-An obvious graphical defect to the upper screen, as you can see from the movie;
-The impossibility to save (the game freezes during the save).
Is there anyone who has the technical knowledge and the desire to give it a good look and fix these issues?
Thanks.

 

[CrashMidnick]

You are lucky because I cannot get Hexen working on DSi (dualhexen and the other one called "mod"). What are your settings for TWL++ ?

The 1st one crash at boot saying it does not find a file (maybe hexen.wad but it is in the right place) and the 2nd one crash on a black screen.

They are working on flashcards.

 

[Nikokaro]

You are lucky because I cannot get Hexen working on DSi (dualhexen and the other one called "mod"). What are your settings for TWL++ ?

It works both using arm9 and arm7 (in this case however it crashes if you increase the graphic details, adding the sky texture under DS option).
And what is this hexen "mod"? Never heard of it. If it's not a bother, try posting its link or uploading it directly here.

 

[CrashMidnick]

It works both using arm9 and arm7 (in this case however it crashes if you increase the graphic details, adding the sky texture under DS option).
And what is this hexen "mod"? Never heard of it. If it's not a bother, try posting its link or uploading it directly here.

Ok, strange. IIRC, only the "mod" version has got saves (needs a folder called /data/hexen. Unfortunately I cannot test on my side, no matter what I do, it does not work on DSi with internal SD.

 

[Nikokaro]

I have some very good news for those interested in the topic.
I have discovered, to my surprise and almost by accident, that using Flipnote as an exploit instead of Memory Pit, DualHexen works perfectly from the SD slot (.nds file on SD root and Hexen.wad in data/Hexen/): there is no longer the graphical defect in the upper screen and you can save without problems. I believe I am the only one to make this incredible discovery, which will surely be of interest to many, even our benefactor @RocketRobz .
It would seem that the camera software, unlike Flipnote, cannot use all the available RAM. I have confirmed this by using, via HBmenu and .argv files, various user Megawads with DS Doom. For example, the most recent version of Freedoom, which used to crash at random points and during saving via Memory Pit, now seems to work perfectly. I am waiting for others to confirm this finding of mine with other data: other games that do not work, or are defective using Memory Pit, with Flipnote Lenny (or other exploits, that I do not know) will work properly. Perhaps this discovery, if confirmed, will be useful to others and to those who know more about it than I do.

 

[elhobbs]

I have some very good news for those interested in the topic.
I have discovered, to my surprise and almost by accident, that using Flipnote as an exploit instead of Memory Pit, DualHexen works perfectly from the SD slot (.nds file on SD root and Hexen.wad in data/Hexen/): there is no longer the graphical defect in the upper screen and you can save without problems. I believe I am the only one to make this incredible discovery, which will surely be of interest to many, even our benefactor @RocketRobz .
It would seem that the camera software, unlike Flipnote, cannot use all the available RAM. I have confirmed this by using, via HBmenu and .argv files, various user Megawads with DS Doom. For example, the most recent version of Freedoom, which used to crash at random points and during saving via Memory Pit, now seems to work perfectly. I am waiting for others to confirm this finding of mine with other data: other games that do not work, or are defective using Memory Pit, with Flipnote Lenny (or other exploits, that I do not know) will work properly. Perhaps this discovery, if confirmed, will be useful to others and to those who know more about it than I do.

I suspect this may be related to this issue -https://devkitpro.org/viewtopic.php?f=38&t=9359
I was having an issue running cheretic on my dsi from the sd with memory pit, but disabling sound capture seems to have resolved the issue.

 

[Nikokaro]

I was having an issue running cheretic on my dsi from the sd with memory pit, but disabling sound capture seems to have resolved the issue

Hi. Do you also confirm that DualHexen works (and can save) via Flipnote Lenny (or other exploit) while via Memory Pit has graphical glitches (as in my video in the opening post) and crashes during saving? Whereas cheretic, I have always used it via Flipnote without problems, so I can't say: however, with It, I cannot play custom wads via argv file.

In any case, according to you, it is not a matter of RAM used, but rather it depends on that (Memory Pit) "sound capture" issue....... I see....

 

[elhobbs]

Hi. Do you also confirm that DualHexen works (and can save) via Flipnote Lenny (or other exploit) while via Memory Pit has graphical glitches (as in my video in the opening post) and crashes during saving? Whereas cheretic, I have always used it via Flipnote without problems, so I can't say: however, with It, I cannot play custom wads via argv file.

I have not tried dual hexen. Memory pit is the only exploit I have for running in dsi mode. I do have an ievo cart but that does not like stuff built with current tools. However the sound capture being enabled could cause any number of issues depending on where the capture buffer resides in the memory heap. Anything ranging from inconsequential to a fatal exception. It would also explain why these issues only occur for memory pit. Where the same file runs fine in ds mode or using other exploits.

 

[CrashMidnick]

I have some very good news for those interested in the topic.
I have discovered, to my surprise and almost by accident, that using Flipnote as an exploit instead of Memory Pit, DualHexen works perfectly from the SD slot (.nds file on SD root and Hexen.wad in data/Hexen/): there is no longer the graphical defect in the upper screen and you can save without problems. I believe I am the only one to make this incredible discovery, which will surely be of interest to many, even our benefactor @RocketRobz .
It would seem that the camera software, unlike Flipnote, cannot use all the available RAM. I have confirmed this by using, via HBmenu and .argv files, various user Megawads with DS Doom. For example, the most recent version of Freedoom, which used to crash at random points and during saving via Memory Pit, now seems to work perfectly. I am waiting for others to confirm this finding of mine with other data: other games that do not work, or are defective using Memory Pit, with Flipnote Lenny (or other exploits, that I do not know) will work properly. Perhaps this discovery, if confirmed, will be useful to others and to those who know more about it than I do.

With the last version of TW++, I can get Hexen to boot
With those options, saves works :
Launch : DS MODE
CPU : 133
VRAML : DSI

I see no glitch after 2-3 minutes of gameplay.

However, only save/load from 1st slot is working (I do not know if this is normal behaviour with this port).

I do not have flipnote on the DSi side, If I launch the exploit from flipnote rom from TW++, lauch the exploit and then launch hexen I only get a white screen.

EDIT : Other slots work but you need to press A once, wait few seconds and then press A again or you will get a fatal error.
EDIT 2 : SAVE/LOAD is really unstable, difficult to predict if it will work or not...

 

[RocketRobz]

I have some very good news for those interested in the topic.
I have discovered, to my surprise and almost by accident, that using Flipnote as an exploit instead of Memory Pit, DualHexen works perfectly from the SD slot (.nds file on SD root and Hexen.wad in data/Hexen/): there is no longer the graphical defect in the upper screen and you can save without problems. I believe I am the only one to make this incredible discovery, which will surely be of interest to many, even our benefactor @RocketRobz .
It would seem that the camera software, unlike Flipnote, cannot use all the available RAM. I have confirmed this by using, via HBmenu and .argv files, various user Megawads with DS Doom. For example, the most recent version of Freedoom, which used to crash at random points and during saving via Memory Pit, now seems to work perfectly. I am waiting for others to confirm this finding of mine with other data: other games that do not work, or are defective using Memory Pit, with Flipnote Lenny (or other exploits, that I do not know) will work properly. Perhaps this discovery, if confirmed, will be useful to others and to those who know more about it than I do.

Even before I found the linked devkitPro thread, I've found that the sound capture registers we're the issue, and TWiLight Menu++ now disables it, as of recent versions.

 

[Nikokaro]

I see no glitch after 2-3 minutes of gameplay.

As already clarified, it was a problem related to the use of Memory Pit as an exploit.

 

[Nikokaro]

My problem now is being able to use the HexenDD.wad (add-on episode) via HBmenu and "command line arguments" within an .argv file, which doesn't seem to work....

 

[CrashMidnick]

My problem now is being able to use the HexenDD.wad (add-on episode) via HBmenu and "command line arguments" within an .argv file, which doesn't seem to work....

You problem is in fact an unfinished port of this game. Even on flashcard it is unstable. Did you see someone playing this add-on in the past with this port ?

 

[Nikokaro]

Did you see someone playing this add-on in the past ?

Naah. I want to be the first, the pioneer of this discovery.....
This official expansion in theory should work, since, like the original ms-dos version, it should support (as also Doom and Heretic) the "-file" argument for playing custom levels.

 

[CrashMidnick]

Naah. I want to be the first, the pioneer of this discovery.....

I hope you will be that guy !
Sorry I cannot help for this,.

 

[Nikokaro]

Ladies and gentlemen, when I put my mind to it, I can perform genuine miracles: yours truly, in all modesty, does not lack a pinch of genius.
As I had hoped, I was able to use the official Hexen expansion (Deathkings of Dark Citadel) with DualHexen, but not using HBmenu and argv files, which are not detected by the software for some reason, but with another, albeit obsolete and little-known, system. I will let the movie speak for itself (I emphasize that it is not a fake, a montage).
Those who are interested in using this or other addons with Hexen, just ask me: I would not like to waste words unnecessarily if no one is interested in the topic.

 

[Nikokaro]

Can @CrashMidnick or someone else tell me if, in your case, the touchscreen of DualHexen (mod version) works? In theory, according to its author, it should allow you to move the character's view and use items, but instead it doesn't work at all. Very strange.

 

[elhobbs]

Can @CrashMidnick or someone else tell me if, in your case, the touchscreen of DualHexen (mod version) works? In theory, according to its author, it should allow you to move the character's view and use items, but instead it doesn't work at all. Very strange.

Apps built with old versions of libnds do not support the touch screen on the dsi. I want to say this is true even in ds mode.

 

[CrashMidnick]

Can @CrashMidnick or someone else tell me if, in your case, the touchscreen of DualHexen (mod version) works? In theory, according to its author, it should allow you to move the character's view and use items, but instead it doesn't work at all. Very strange.

Both versions are working on my side (tested on DSi dual hexen standard + mod). I can look around and view/select items.

For Deathkings of Dark Citadel addon, I am not interrested because to be honest I do not really like Hexen but maybe people in the future would like to know the solution

EDIT : Tested on DS lite + DSTWO = working too

 

[Nikokaro]

Both versions are working on my side (tested on DSi dual hexen standard + mod). I can look around and view/select items.

Then I don't understand why it doesn't work on my DSi: this is unbelievable! And then @elhobbs just stated that in fact it should not work on DSi. This is getting more and more complicated....