Good day,
I've been using REWASD for some time now, mainly because of its support for remapping the paddle buttons on the Series 2, which was easier to use than a driver I cobbled together to remap them.
But there has been a persistent issue that rears its ugly head occasionally that is incredibly frustrating. Especially given that the main purpose of the software is to be able to apply profiles to the controller you are using.
REWASD will sometimes invalidate the profile that you are using, what I mean is that it will completely empty out any of the painstaking mappings you have made and instead overwrite them with a blank profile, which is irrecoverable. Because I've had this issue before I usually try to make sure I have backups of profiles, in this last instance I had created and tested some new profiles with some new games but I had failed to back them up.
It does not just wipe out the profile you are currently using, but even if you switch to another one, it will also empty that one out, they all will consistently have the following contents:
{
"schemaVersion": 3.0,
"appVersion": "6.4.0",
"config": {
"appName": "Game",
"minTimeUnit": 1
},
"devices": {
"hardware": [
{
"id": 1,
"name": "gamepad",
"default": {
"touchpads": [
{
"id": 2,
"mode": "analog",
"trackballFriction": 50
}
]
},
"applyToPhysicalPriority": true
}
],
"virtual": {
"gamepads": [
{
"id": 1,
"type": "360"
}
]
}
}
}
Which appears to be just a default template.
This last time I had the issue, I was making a very small change to a paddle button, and when attempting to save the profile I received a message that it wouldn't apply an empty profile even though on the UI it was displaying the correct mapping for the profile. However when navigating away and back to the profile it would be empty.
I checked the .etl files in the log directory, but there isn't formatting information included with them so I have no idea what the event's actually mean.
Is this a known issue with a solution?
I've been using REWASD for some time now, mainly because of its support for remapping the paddle buttons on the Series 2, which was easier to use than a driver I cobbled together to remap them.
But there has been a persistent issue that rears its ugly head occasionally that is incredibly frustrating. Especially given that the main purpose of the software is to be able to apply profiles to the controller you are using.
REWASD will sometimes invalidate the profile that you are using, what I mean is that it will completely empty out any of the painstaking mappings you have made and instead overwrite them with a blank profile, which is irrecoverable. Because I've had this issue before I usually try to make sure I have backups of profiles, in this last instance I had created and tested some new profiles with some new games but I had failed to back them up.
It does not just wipe out the profile you are currently using, but even if you switch to another one, it will also empty that one out, they all will consistently have the following contents:
{
"schemaVersion": 3.0,
"appVersion": "6.4.0",
"config": {
"appName": "Game",
"minTimeUnit": 1
},
"devices": {
"hardware": [
{
"id": 1,
"name": "gamepad",
"default": {
"touchpads": [
{
"id": 2,
"mode": "analog",
"trackballFriction": 50
}
]
},
"applyToPhysicalPriority": true
}
],
"virtual": {
"gamepads": [
{
"id": 1,
"type": "360"
}
]
}
}
}
Which appears to be just a default template.
This last time I had the issue, I was making a very small change to a paddle button, and when attempting to save the profile I received a message that it wouldn't apply an empty profile even though on the UI it was displaying the correct mapping for the profile. However when navigating away and back to the profile it would be empty.
I checked the .etl files in the log directory, but there isn't formatting information included with them so I have no idea what the event's actually mean.
Is this a known issue with a solution?
Comment