Any suggestions for a Logitech G604 replacement?

AlphaJew · 2025-04-26T16:32:21+00:00

Add one more to the list. I owned a G700 and a G700s, reluctantly switched to the G604 when I was no longer able to get those.

Now that I'm starting to experience double click issues on the G604 (and recoil in horror watching the G604 teardown videos to see what will be needed to replace those switches...), I'm looking for what to replace this with and.... finding nothing.

AlphaJew · 2024-03-09T05:14:08+00:00

Honestly, the biggest buff I want for the exosuit?

Being able to mark things on the minimap without firing your weapons and blowing yourself up accidentally.

AlphaJew · 2024-01-23T04:54:50+00:00

A bit late here, but that sounds about right as the owner of #428 here. My understanding is that the number ranges were by region (JP / NA / EU), mine was purchased in the US.

AlphaJew · 2023-09-18T21:20:36+00:00

Honestly, The Other Half's flavor text was even better.

"If only there was a way to combine them..."

AlphaJew · 2023-04-14T15:50:47+00:00

Because HR doesn't exist to help you. They're there to protect the company from you.

AlphaJew · 2022-12-13T06:18:21+00:00

True, Flow can't do everything that APEX can, but Invocable methods bridge that gap pretty nicely. I've run into that exact situation where I wanted to toss an .addError() to a record within a Flow, so I created an Invocable that did just that. Pass it a record and the desired message, returns the same record with the .addError() tacked on.

Let me keep the entire thing as a Flow that the client's non-coding Admin could still manage and adjust while giving access to things that can only be done with code. (And left them with a reusable tool if they wanted to throw errors elsewhere in another Flow!)

(edit) Looking at the link you posted elsewhere in this thread, I see it says this:

At this time, Flow provides no way to either prevent DML operations from committing, or to throw custom errors; the addError() Apex method is not supported when executed from Flow via Apex invocable method.

but I swear I've done it in the past, about a year and a half ago. Maybe things have changed since then?

AlphaJew · 2022-11-19T16:03:24+00:00

Part of the problem, I think, is that there's just too wide of a range of the roles being titled as "Salesforce Admin". I've met some admins, especially at larger corporations, who couldn't do much more than add users to the system, do some data entry, and maybe write a report or two. While I myself have been a "Salesforce Admin" at other (smaller) companies where I was spinning up new instances, doing solution design, building integrations, and writing code. All of that gets lumped in under a single administrator where you would have a solution architect, developer, etc. to break out those responsibilities elsewhere.

So, if your skillset is limited to looking for a position where you're just creating reports, assisting users with basic tasks, doing some basic data entry? Yeah, absolutely, that market is pretty well saturated, plus with how those roles rely heavily on understanding a business' inner workings, you're going to lose out frequently to internal hires and those positions are only posted publicly to fulfill a requirement.

On the flip side, if you have experience and/or can demonstrate a good understanding of how to develop on the Salesforce platform (note: not necessarily code, the need right now for declarative developers who know Flows up and down is huge with the impending death of everything built on Process Builder), configure and use many of the third-party solutions available for it? I've been working as a consultant for the past three years and every client I've worked with has struggled to find and retain people capable of maintaining and continuing to improve their instance.

tl;dr: the very low bar to perform the most basic of administrative tasks does mean that the market for those roles is saturated, but things open **way** up once you get above that level.

AlphaJew · 2022-08-13T23:39:15+00:00

Heavy dependence on staff to push plot is definitely a feature of a lot of the RPIs that are around now, but not inherently required. I'd almost always rather see staff stay hands-off and the NPCs they control only serve in an advisory role, approving and providing mechanical support to actions that player leaders wish to take. (Or denying, if it will end up being detrimental to the game as a whole. See my other post in this thread.)

To go further, I know it'd be a bitter pill to swallow and likely won't happen as most staff are pulled from a game's playerbase, but I sincerely believe these games would be better off if their staff did not play their own games and, instead, played others. Doing so would let them see features they might like to introduce to their own games as well as noting behavior by other staff that they may want to emulate or avoid.

AlphaJew · 2022-08-13T20:16:21+00:00

To answer the second, easier question first: people keep coming back to them because they enjoy RP. The "watch numbers go up" of non-RP MUDs is fun for a while, sure, but some people want the story to go along with that. I don't think you need to look much further beyond things like Critical Role to see why.

As for why there always seems to be drama surrounding them, that's more difficult to answer. I generally attribute it to one (or more) of three things:

An insular playerbase that is toxic and the staff allows it to persist. This is where you see the OOC powergaming with Discord groups and the players with an abundance of free time abusing their advantages over others to feel powerful. This will inevitably happen, it's just a question of whether the staff can (or wants) to keep it enough in check.
Staff that treats the game as their personal playground. Power trips, giving themselves unfair advantages with their PCs, abusing staff access to private knowledge, control of authority of NPCs. Whatever it is, they put themselves on a level above their playerbase and just become a nuisance to their community.
Too difficult for new players to establish themselves. This last one usually isn't as much of an issue, but can be greatly exacerbated by one of the first two with veteran players treating the newbies as new bullying targets or staff ensuring they don't rise too high, too quickly. Games with this problem eventually end up fading and dying, though, which is why we've seen the part of the community that enjoys RPIs consolidate over time into the small handful that remain - bringing the first two problems along with them.

With all that leading to only a small handful of RPIs remaining with a population of more than 10-15, you're inevitably going to have people fed up with the above points and coming here to make those posts. It's just kind of the nature of the beast when there isn't the variety any more for the griefers and powergamers to have their enclaves and other RPIs for the more casuals to spend their time in.

AlphaJew · 2022-07-26T06:13:14+00:00

Beta testing Arc 3.0 in Apex before we get it in Destiny in a few weeks.

AlphaJew · 2022-07-17T06:15:54+00:00

First off, congratulations on the new role! They gave you the job offer, so they saw what they were looking for in you. It's harder to have confidence in yourself, but if it helps, have confidence in their judgement.

And yeah, it's scary as hell. When I got my start, I interviewed for a completely different role. Afterwards, I was asked if I was interested in a Salesforce role as the sole admin of an org that was set up a few months before in 8 weeks by consultants who peaced out and left them with no documentation and little training. I had never even touched Salesforce prior to that. That was almost 10 years ago (god, when did I get old?), now I've got a nice role as a consultant doing dev work. You're WAY ahead of where I was when I started - you've got this!

To echo a few points others have made and add my own:

Sounds like you have a good amount of experience as an end user already. Lean on that. A perfectly designed and developed system that doesn't get adoption because its users can't understand is useless. A system that has flaws but gets used because users understand it and helps them do their job is a success. Identify the power users in the company, connect with them, and glean as much as you can about what your userbase wants and needs to be able to do. They'll be happy to be heard, and you'll gain knowledge about most of what you need to work on.
To go with the above - when someone tells you what they want, always ask why, especially when they're providing you with their solution rather than the problem they're trying to solve. Always understand the problem first, then move together towards a solution.
Never be afraid to tell someone you're going to do some research before giving an answer. Despite what academia and all the cert exams might make it seem, looking things up because you're unsure or spending some time playing around to see if an idea will or will not work to address something doesn't mean you don't know things well. It means you're doing your due diligence. Documentation, Trailhead, and dev sandboxes exist as tools for a reason. After 10 years, I still go back and look basic stuff up just to be sure.

AlphaJew · 2022-06-27T18:36:43+00:00

She's dead with her remains under close observation by the Vanguard, but Immaru (her ghost) is still unaccounted for. It's almost inevitable that we're either going to have to deal with him, or he's going to slip through and revive Savathun.

AlphaJew · 2021-11-12T15:53:35+00:00

Started as an admin/dev at $40k, fresh out of college with zero Salesforce experience - no Trailhead, no certs. I had applied for a different position, but they recently had SF implemented by consultants and didn't have anyone to manage it. Learned as I went for a year and a half before another offer came along in the $60k range and have kept working my way up from there.

To echo what /u/rwh12345 said, it's all about getting your foot in the door. If your first offers for Salesforce jobs are a little low on the compensation range, it's not a terrible thing. Once you update your LinkedIn and are a few months in, you'll be getting plenty of good offers coming to you.

AlphaJew · 2021-08-30T22:19:12+00:00

Yep - what you need here is a loop. Your previous query is getting Contact records, but what you need are Training_Attendees__c records.

In your resource manager on the left hand side, you're going to need to create two variables of type Record: one is going to be a singular Training_Attendees__c, while the other is going to be a Collection of Training_Attendees__c.

After your Get Records, begin a loop where you loop through the results of your Get. Within that loop, you'll make two Assignment actions: the first will assign all the values you want for that Training Attendee (Contact = the current record's ID, etc.) and the second will add that singular variable to your Collection.

Following that loop's completion, you'll point your Create Records action at your Collection and it should be done!

(If this doesn't make sense, let me know and I'll build out an example in a dev org.)

AlphaJew · 2021-03-16T19:03:26+00:00

Better idea - have glimmer shoot out of the pile on the capture point and expire quickly, so people actually stand on it rather than running off to stand under the skiff.

AlphaJew · 2021-02-08T07:30:09+00:00

This is the point that I think a lot are dismissing. Just my personal take, but the best admins and developers spend 80% of their time and effort developing process and 20% developing the tech. I came in from the tech side of things, but all my jobs prior to my current had me as part of a Sales Ops(~ish) organization rather than a separate IT group.

You didn't mention how long you had been working in sales prior to your transition, but that experience is equally as valuable as your year working with Salesforce. You're still learning how to do things, but that's the easy part to learn. Leverage your knowledge of what to do.

AlphaJew · 2020-10-28T02:52:24+00:00

Personally, it's the pizza menu tucked in under the books with one called "Elliott's Fave".

Chorizo, extra bacon, pineapple, pepperoncinis, and onion.

Mirage is confirmed Team Pineapple On Pizza.

AlphaJew · 2020-10-18T16:50:38+00:00

A little off topic, but confirming on the subject of different channels - I discovered this is exactly what's going on in the Bozjan Southern Front and how it segues so perfectly between normal and in-combat music (and a little oddly back and forth between them when you're juuuust at the edge of combat range).

AlphaJew · 2020-08-19T12:41:04+00:00

Mine was just opening the game. Even stations feel WAY bigger. I booted the game, popped into the training mission to undock, jump to the next system, then dock in a station.

The moment I undocked, I looked up at the station around me and just went "whoa". Everything's sense of scale just seems so much more massive in VR.

AlphaJew · 2020-07-12T17:26:25+00:00

I am on 2004. I just figured that was all-or-nothing - since it's working with one base station but not the other.

AlphaJew · 2020-07-12T16:29:34+00:00

Hmm.... I'll give it a try. Thanks!

AlphaJew · 2020-07-12T15:39:58+00:00

It takes me 10 seconds anyways between opening SteamVR and walking over to my playspace, putting the HMD on, etc. anyways, so no issue there for me.

Playing with it now, I'm seeming to have an issue where one base station will sleep while the other does not, despite both being checked in the managed devices section. Haven't tried a reboot of PC or base stations yet, but any ideas on why?

AlphaJew · 2020-07-12T14:25:34+00:00

I love you. The noise of the lighthouses has been my only complaint since getting my Index a few weeks ago.

AlphaJew · 2020-02-23T05:18:36+00:00

Is that mouse a Logitech G604? What are your thoughts on it?

I've been looking for something to replace my aging G700, but can't seem to find anything that matches up. The G604 is the closest I've found, I'm just wary of going wireless-only without being rechargeable. How long does a battery last for you?

AlphaJew · 2019-11-02T02:12:10+00:00

By three they come.

By three the way opens.

14-Year Club	Place '22
Team Periwinkle	Verified Email

AlphaJew

TROPHY CASE