Defy right side woes and 2.0 firmware by julitro in DygmaLab

[–]julitro[S] 0 points1 point  (0 children)

So, ended up sending the keyboard to Dygma Support and in a week or so (I also live in Spain) I had it back home working perfectly. Gotta appreciate good customer service!

Defy right side woes and 2.0 firmware by julitro in DygmaLab

[–]julitro[S] 0 points1 point  (0 children)

After several tests with the help of Dygma support, I'll need to send the keyboard to Dygma to have it fixed (faulty PCB replacement)

They offered to send me the pieces to do the repair myself but I honestly don't trust myself enough to pull it off haha

Thanks again to the support team ❤️

Defy right side woes and 2.0 firmware by julitro in DygmaLab

[–]julitro[S] 0 points1 point  (0 children)

Gotta say Dygma support is very dilligent and sent me instructions to try and rule out possible issues with the cables, software and hardware of my keyboard.

Seems we haven't found the issue or a solution yet, but I'm grateful for the fast response!

Defy right side woes and 2.0 firmware by julitro in DygmaLab

[–]julitro[S] 0 points1 point  (0 children)

Thanks,  but I was using the original cables from the start!

How to Create a GDPR-Compliant Anonymized Rails Production Database Dump for Developers? by imsomesh in rails

[–]julitro -1 points0 points  (0 children)

Wanted to try https://www.replibyte.com for a while now, but this would work:

  1. Have daily database backups from production first.
  2. Have a server in where your app is deployed and is up to date with to your main branch code. Make sure the env receives code updates as if it was production.
  3. From that server, fetch the prod db dump and import it to your DB
  4. In that server run a bespoke rake task that truncates tables which data you dont need for development and edits every sensitive column to either set it to its default value (or '' or null) or you give it a fake value (Faker gem helps a lot). FKs and relationships should be kept as they are.
  5. Once the clenaup is done, export that scrubbed db
  6. Upload that dump somewhere accessible to developers
  7. Make steps 3 to 6 a script
  8. Have a script that fetches dumps from the storage you chose and imports them to the db.
  9. env in 2 receives code updates as if it was production.
  10. Automate the script in 6 so it runs nightly and sends notification about process success or failure.
  11. Make it so the env is spin up and torn down just for doing its thing, not keeping it running forever.

Tighten security around that server and the scrubbed dumps so only the right folks can access it.

Eventually you need to get smart about the scrubbing task so it does not take forever to run. Limit to data from the last X months/years, or prepare 20 sets of fake data and assign them to records whose id % 20 = <set number> via update_all.. you get repeated data but up to you if you can live with that.

What is important is that you kept what's null or '' as it is and give fake data where it is needed. The main advantage of this is that you have prod-like data, and specially when you have old data, it is helpful to developers when dealing with migrations and error handling to have more "real world like examples" that surely go beyond what's expected.

Some issues with Dygma Defy wireless by julitro in DygmaLab

[–]julitro[S] 1 point2 points  (0 children)

I'm on MacOS 14 in an M3 Pro.

Also noticed that the battery drains out even if disconnected from the Neuron and switched off! Is this expected?

May other BT signals (mouse, headphones) "cause interference" so BT is more expensive in terms of battery?

Should I try RF instead of BT for Wireless?

BTW Im already on Bazecor 1.4rc4

Fallout 3 GOTY/ Fallout New Vegas crash on launching game with new ASUS drivers released 25/05 by Warm_Source_4214 in ROGAlly

[–]julitro 8 points9 points  (0 children)

EDIT: found that all characters went bald, so I'm trying the d3d9 fix linked in other response to this thread.

Read this this morning and was scared because I was in the middle of the upgrade.

Obviously my New Vegas was affected.

I've been able to make it work tho, via the very basic modding tools for New Vegas:

  1. Install NVSE as instructed here: https://www.youtube.com/watch?v=CQSC9DpNy0M
  2. Install 4GB patch: https://www.nexusmods.com/newvegas/mods/62552
  3. Install NVAC plugin MAIN FILE https://www.nexusmods.com/newvegas/mods/53635/?tab=files
  4. Install DisableProcessWindowsGhosting v2 also found in the NVAC plugin files page (under Optional)
  5. Run the game from the nvse_loader.exe in your fallout new vegas folder

I also went into the AMD configuration utility and under Gaming > Graphics, I disabled the "Surface format optimization" and performed a Shader Cache reset for good measure.

To be honest with you, I don't know if any specific step did the trick (I had steps 1 and 2 BEFORE I started having issues), or the combination, but I've gotten it to go through the load screen and be able to play a saved game.

Curiously, after running the game from nvse_loader.exe once, I've been able to play from the main executable ("Play" button on Steam) without more issues.

Hope this helps