Yes, in the filemanager main window (root), insert the disc and you will see a disc icon on top of the devices list, click triangle button in it and you will see the option
How difficult would it be to add a group of multiple values to select from for one address into the pnach based system?
since the values are already known, with a label set for each selectable value.
Something like PEC/CEP's drop down menu for ePSXe.
I cant tell how dificult could be to implement that feature, this is mostly a question for @Zar but i think your theory should work
The first requirement for something like this to work is to create a database with all that info, the collections of pnach widescreen patches contains the address that needs to be patched in every game, so that collections works as a database in itself, we could read that values from the pnach files (so in some way we are accessing the database to recover that info) and after that... well there are several things that can be made
Is posible to convert the data into the official CONFIG format, this way the patch is applyed in a "volatile" way (not permanently, so we are not modifying the ISO)
And is also posible to allow the user to enter different values for them, the most noob-friendly way would be to offer a selection of predefined screen sizes, but allowing the user to enter any value is something handy for experimental purposes
Yes, in the filemanager main window (root), insert the disc and you will see a disc icon on top of the devices list, click triangle button in it and you will see the option
I cant tell how dificult could be to implement that feature, this is mostly a question for @Zar but i think your theory should work
The first requirement for something like this to work is to create a database with all that info, the collections of pnach widescreen patches contains the address that needs to be patched in every game, so that collections works as a database in itself, we could read that values from the pnach files (so in some way we are accessing the database to recover that info) and after that... well there are several things that can be made
Is posible to convert the data into the official CONFIG format, this way the patch is applyed in a "volatile" way (not permanently, so we are not modifying the ISO)
And is also posible to allow the user to enter different values for them, the most noob-friendly way would be to offer a selection of predefined screen sizes, but allowing the user to enter any value is something handy for experimental purposes
is there a way i can use managunz but load ps1 games through webman? games with multiple tracks don't play music if loaded from managunz. they work fine if loaded from webman (xmb).
Yes, in the filemanager main window (root), insert the disc and you will see a disc icon on top of the devices list, click triangle button in it and you will see the option
I cant tell how dificult could be to implement that feature, this is mostly a question for @Zar but i think your theory should work
The first requirement for something like this to work is to create a database with all that info, the collections of pnach widescreen patches contains the address that needs to be patched in every game, so that collections works as a database in itself, we could read that values from the pnach files (so in some way we are accessing the database to recover that info) and after that... well there are several things that can be made
Is posible to convert the data into the official CONFIG format, this way the patch is applyed in a "volatile" way (not permanently, so we are not modifying the ISO)
And is also posible to allow the user to enter different values for them, the most noob-friendly way would be to offer a selection of predefined screen sizes, but allowing the user to enter any value is something handy for experimental purposes
Can you guide me on how to make a CONFIG file then?
I just copy a premade one as a doner & edit away?
You can put multile entries in of the same code as long as they have different names?
Can you guide me on how to make a CONFIG file then?
I just copy a premade one as a doner & edit away?
You can put multile entries in of the same code as long as they have different names?
Do the 480P patches work differently for non bc PS3? everyone i've used has shifted the game screen into the middle, View attachment 30622
whilst games with just the 480P Triangle+X combo activated appear fine. View attachment 30623
Can you guide me on how to make a CONFIG file then?
I just copy a premade one as a doner & edit away?
You can put multile entries in of the same code as long as they have different names?
Do the 480P patches work differently for non bc PS3? everyone i've used has shifted the game screen into the middle, View attachment 30622
whilst games with just the 480P Triangle+X combo activated appear fine. View attachment 30623
To "port" pnach patches to the official CONFIG format is required to understand both formats, keep in mind the pnach files are always "patches" but the CONFIG format allows to do more things, i dont know much about pnach format, but for an introduction to the CONFIG format take a read at this tutorial https://www.psx-place.com/threads/w-i-p-configs-for-ps2_netemu-explained.15034/
For an overview of all the commands availables to be used in a official CONFIG.. the most intuitive way is to take a look at this table https://www.psdevwiki.com/ps3/Talk:PS2_Emulation#PS2_Emulators_Config_Commands
As you can see netemu (the emulator 100% software based) can use a lot of commands, up to command ID= 0x50
But as said before, most of the times is only need to use the commands intended to apply patches (to the ISO, to the EE memory, etc...), so you only need to learn how works a few of the CONFIG commands, so there are only a few rules to remember, about how to do the endianess byte flipping, values conversions, values lenghts, etc...
The best way to learn how the official CONFIG works is by keeping an eye at this thread https://www.psx-place.com/threads/compatibility-list-ps2-on-ps3.1306/
There are many experimental CONFIG published on it, take one of them (a little one) and try to understand how it was made
@Zar im looking at the settings to "customize" the filemanager "root" window and there is something that is causing lot of confussion, the million dollars question is... what's the difference in between the names displayed with the option "Mount point" and "Device" ?
In my PS3 both things displays the same names (dev_flash, dev_hdd0, dev_hdd1, etc...), it seems in current managunz version "Device" is displaying "Mount point" as a fallback
Im guessing is because the "device" is not implemented yet because is related with the problems you was having to recover "metadata info" (in general) from the different devices and filesystems ?
Not sure if you made some progress in that direction, but incase the "device" names are not supported yet i suggest to delete (or comment) all the options where appears the "Device", there are several
-----------------------------
And... mgz settings > root display > custom style (and the other predefined styles) > #x Row content >>>>> Capacity bar width (and his variants)
Can you add the polygonal arrow at the left of the setting: "Capacity bar width" to indicate that is a children of the previous "Row Content" setting ?
I guess is needed to add the DrawChildArrow() when is created the menu item with: add_item_MENU(STR_FM_CB_WIDTH, ITEM_TEXTBOX);
Another suggestion related with the filemanager "root" window, im not sure if i mentioned this to you before, incase i did sorry for insisting in it, im mentioning it now because incase you like the suggestion i hope is going to be relativelly easy to implement it
Is related with how is used the option "Mount /dev_blind", and the black LOCK.PNG icon overlapped on top of a corner of the devices icons to indicate his write access
The way how it works now is we enter in filemanager, and by default is displayed the name dev_flash and the LOCK.PNG icon overlapped in a corner of FLASH.PNG icon, this works fine, is intuitive
If we press triangle to open the options, we can select "Mount /dev_blind" and this makes us return to the "root" window where appears an additional FLASH.PNG icon with the name "dev_blind" but without the LOCK.PNG black icon overlapping a corner of FLASH.PNG, this works fine, is intuitive
But there are two problems:
1) Is displaying 2 icons for the same partition (dev_flash and dev_blind)
2) If we click in triangle (to make appear the options) we dont have an option to "Unmount dev_blind", this feature is not implemented, and we dont even have an string for it in the translation files
---------------------------
My goal with this suggestion is to make this the most easy and intuitive posible, in a noob-friendly way by adding this new strings:
STR_LOCK_FLASH {Lock dev_flash}
STR_UNLOCK_FLASH {Unlock dev_flash}
As you can see im using the name "dev_flash" in both modes, because the presence of the black LOCK.PNG icon is intuitive enought to tell to the user that the flash partition is locked (literally)
Internally managunz could use the alternative devices names for dev_blind, deb_rebug, dev_habib, dev_johndoe, but the final user doesnt needs to know that names
Is the kind of technical "slang" that is a bit pointless and could be a bit confusing for noobs. But the other people with more experience are going to deduce what means the black LOCK.PNG icon
The "mount point" name displayed in the filemanager root window should be always "dev_flash", and it should be only 1 apparence of it in the device list, with only 2 states posibles, locked or unlocked (indicated by the presence of the LOCK.PNG icon)
If the dev_flash is unlocked (because we used the "Unlock dev_flash" option previouslly) when we enter in the options menu it should appear the other option to "Lock dev_flash"
In other words... the presence of the LOCK.PNG and the strings STR_LOCK_FLASH / STR_UNLOCK_FLASH should "switch" together
@Zar I found a minor bug in managunz. If all filters except favorite is disabled, it will say "No games found. Adjust your filter" until you press left on the d-pad. Speaking of filters, would it be possible to add an option to reset the position of the filter box?
Another suggestion related with the filemanager "root" window, im not sure if i mentioned this to you before, incase i did sorry for insisting in it, im mentioning it now because incase you like the suggestion i hope is going to be relativelly easy to implement it
Is related with how is used the option "Mount /dev_blind", and the black LOCK.PNG icon overlapped on top of a corner of the devices icons to indicate his write access
The way how it works now is we enter in filemanager, and by default is displayed the name dev_flash and the LOCK.PNG icon overlapped in a corner of FLASH.PNG icon, this works fine, is intuitive
If we press triangle to open the options, we can select "Mount /dev_blind" and this makes us return to the "root" window where appears an additional FLASH.PNG icon with the name "dev_blind" but without the LOCK.PNG black icon overlapping a corner of FLASH.PNG, this works fine, is intuitive
But there are two problems:
1) Is displaying 2 icons for the same partition (dev_flash and dev_blind)
2) If we click in triangle (to make appear the options) we dont have an option to "Unmount dev_blind", this feature is not implemented, and we dont even have an string for it in the translation files
---------------------------
My goal with this suggestion is to make this the most easy and intuitive posible, in a noob-friendly way by adding this new strings:
STR_LOCK_FLASH {Lock dev_flash}
STR_UNLOCK_FLASH {Unlock dev_flash}
As you can see im using the name "dev_flash" in both modes, because the presence of the black LOCK.PNG icon is intuitive enought to tell to the user that the flash partition is locked (literally)
Internally managunz could use the alternative devices names for dev_blind, deb_rebug, dev_habib, dev_johndoe, but the final user doesnt needs to know that names
Is the kind of technical "slang" that is a bit pointless and could be a bit confusing for noobs. But the other people with more experience are going to deduce what means the black LOCK.PNG icon
The "mount point" name displayed in the filemanager root window should be always "dev_flash", and it should be only 1 apparence of it in the device list, with only 2 states posibles, locked or unlocked (indicated by the presence of the LOCK.PNG icon)
If the dev_flash is unlocked (because we used the "Unlock dev_flash" option previouslly) when we enter in the options menu it should appear the other option to "Lock dev_flash"
In other words... the presence of the LOCK.PNG and the strings STR_LOCK_FLASH / STR_UNLOCK_FLASH should "switch" together
You are talking about the novices, I agree, it's more intuitive. But if I do this the advanced user or even a regular user will be confused, it has been several years we used dev_blind. For example, me if I see dev_flash in the full path I know it's locked.
I also wanted to add the lock icon somewhere in the window when we browse the locked path, probably at the extrem top/left.
@Zar I found a minor bug in managunz. If all filters except favorite is disabled, it will say "No games found. Adjust your filter" until you press left on the d-pad. Speaking of filters, would it be possible to add an option to reset the position of the filter box?
You are talking about the novices, I agree, it's more intuitive. But if I do this the advanced user or even a regular user will be confused, it has been several years we used dev_blind. For example, me if I see dev_flash in the full path I know it's locked.
I also wanted to add the lock icon somewhere in the window when we browse the locked path, probably at the extrem top/left.
While i was thinking in this suggestions i was trying to imagine the potential complaints about not using the name dev_blind anywhere and honestly i coould not imagine any
What you mentioned about not being able to recognize his "writable" state by looking at the path name when we are located in a subfolder... well, is the only flaw so far but i dont think is so important, i think the more experienced users are going to realize about it, and as you mentioned displaying the LOCK.PNG inside the subfolders could be a solution for that
I think the benefits of using only the name dev_flash are bigger than the small confusion it could cause to experience users
For the noobs is going to be better, and for everyone in general, im not only suggesting it for noobs, is also because i would like it too, this is one of the times when i think the easyest solution is going to be the better
@Zar I found a minor bug in managunz. If all filters except favorite is disabled, it will say "No games found. Adjust your filter" until you press left on the d-pad. Speaking of filters, would it be possible to add an option to reset the position of the filter box?
The filter box can be moved around with the right left stick in all the interface modes: XMB, FLOW2D/3D, LIST, GRID (and managunz will remember his position for the next boot)
The way how works the checkboxes inside the filter box are a bit non-intuitive... i was discussing that with zar time ago but i dont remember well
The problem is when you enable the checkbox for "favorites" managunz is going to display only the games that was marked as favorites (doing it individually for every game in the game settings for that specific game)
Incase you dont have any game marked as favorite then is not going to be displayed any game, instead of that it will display the warning text "No games found. Adjust your filter"
@Zar I found a minor bug in managunz. If all filters except favorite is disabled, it will say "No games found. Adjust your filter" until you press left on the d-pad. Speaking of filters, would it be possible to add an option to reset the position of the filter box?
Thx, do you mind if i rename the strings like this in the spanish translation ?, im guessing this would complete the "noobification" i was suggesting
STR_MOUNT_DEVBLIND {Desbloquear dev_flash}
STR_UNMOUNT_DEVBLIND {Bloquear dev_flash}
Im still curious about this, how is working ?, all i know is by looking at the names displayed by managunz for the "Mount point" and "Device" it seems one of them is using the other as a "fallback". But which one was fully implemented ?
And it seems it happens too with the "label"
I mean... the non-removable devices doesnt have label... it seems the only devices that allows a label are the USB devices (i have one named "STICK 4GB"). If i select label (only, located at left of the line) the list looks like this
dev_flash <--- it seems is displaying "mount point" as a fallback ?
dev_flash2 <--- it seems is displaying "mount point" as a fallback ?
dev_flash3 <--- it seems is displaying "mount point" as a fallback ?
dev_hdd0 <--- it seems is displaying "mount point" as a fallback ?
dev_hdd1 <--- it seems is displaying "mount point" as a fallback ?
STICK 4GB <--- real label
app_home <--- it seems is displaying "mount point" as a fallback ?
host_root <--- it seems is displaying "mount point" as a fallback ?
----------------
Edit:
Btw, can you add a new combo to display: Mountpoint (Label) ?
I think is going to be my favourite to locate at left on the first row
