• 10 Posts
  • 79 Comments
Joined 3 years ago
cake
Cake day: July 18th, 2023

help-circle
  • I will start by saying that I have no idea what their plans are and I am not a game or game engine dev.

    how do you have the same skin in multiple games for different character or items models?

    I think what we’ll see is the model and mesh of the skins will be loadable by the game via the engine. I’m assuming they’ll have a standard that contains the hitbox and model/mesh to put on the character. Then the game dev could tweak gobally the scaling (as an example) to make all skins fit nicely into their game. Same for guns and such. But game devs who want to opt in[1] to this will have to use the engine API to make it work.

    Are they going to update every game when there is a new skin released

    I would assume that the game itself won’t need to be recompiled or updated but rather the engine will download the newest skins in some common and reusable place. And then the engine swaps one model for another.

    [1] my suspicion is that the tech will be licensed to the game makers. Especially if they plan on allowing copyright characters (like Marvel characters).

    And again, please take everything I said with some salty grains or something as I am only speculating.


  • Epic shared plans for “portable content, codes and economies” between UE-developed games, with Fortnite slated to be the first real proof of concept. In Fortnite’s case, portability will allow cosmetics obtained or purchased in-game to be used in other UE games and vice versa. Additionally, UE6’s cross-game social link feature will allow players to be connected to one game, but voice chat with people playing another.

    The first part seems like a new concept we haven’t seen in other games. Buy one skin, use it everywhere. I bet they’re going to fuck it up with their greed somehow, but it’s a neat concept and provides more value to people who buy skins.

    The second part, and last sentence, is basically just discord, team speak, etc. I don’t buy or use Epic’s stuff, but if I understand it correctly, some dumbass thought it was a good idea to only allow voice channels for people playing the same game 🤣🤣🤣






  • Yes, this is 100% a scam or rather, fraud (and may be illegal where you live).

    He explains the con right in the follow-up email.

    The reason for this proposal is that I had been working with several US collaborators on regular US software engineering roles using their profiles due to the high rate. After securing the positions, the work is subcontracted to me.

    Let’s break this down.

    He gets people who would have nice resumes (or profiles,… like a young fella fresh outta college) to apply for tech jobs. He’s looking specifically for US tech jobs because of the “high rate” in which he means the jobs pay a high hourly rate/wage.

    Once the company hires you, you subcontract (aka pay him) to do the work. Of course he’s probably going to say something like, well you keep 20% of the “high rate” for yourself.

    The following is only speculation

    Since he’s asking you about interviews and team meetings, I have a feeling he’s not getting a lot of success recruiting “collaborators” in the US and likely thinks getting someone already in the US to recruit other will be easier (no language barrier, no international issue, etc). Having an American front man for this scam is likely going to make recruitment easier.


  • I don’t know how you add a call to an API that doesn’t exist

    As far as I know, these messages are passed to the portal using dbus. So the app could just fire the correct dbus message with correct parameters (you can find the correct values in the Wayland specs). The portal, used by the compositor, then takes the message and runs the requested action or returns something like not implemented or unknown method.

    The trickier part is testing when no portal supports the API calls.

    But yeah, interoperability between systems can be a pain in the ass.

    The process is analogous to sending an http request. Your app sets up the httpclient and points it to a URI and after sending the request you get back either the content with 200 status or 404. If you get 404 you can show the user a message like “this website doesnt support feature xyz”


  • not a single one of those compositors implement the entire API surface you need.

    Aegis has requested that those of us who wish to not see Talon on Linux die out do the following:

    • Do not, for any reason, discuss Wayland support with him;
    • As a community, gather together, and successfully implement the entire API surface needed for Talon on GNOME, KDE, and wlroots,

    At which point a new Wayland backend will be considered for Talon.

    I agree that it’s not up to Talon to implement the missing APIs in the compositors. However, I think the dev is doing a disservice to the users of Talon by not adding wayland support (ie making the calls to the APIs Talon needs to function). If Talon used those wayland protocols, users could point to the software and say it’s “not working on compositor because the compositor is missing wayland protocols”.

    IMO its a much easier sell to the compositor people when they know a useful piece of software is actively trying to target those APIs.

    That being said, I sure hope the situation improves. The state of accessibility on wayland is pitiful.












  • mrbn@lemmy.catolinuxmemes@lemmy.worldKDE did a funny
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    2 months ago

    I believe so, I calculated the area of the NHL rinks using lots of popsicle sticks, a flashlight (cause the lights were off), and a broom. In hindsight maybe I should have included a calculator but I ain’t no nerd! /s

    Either way, that’s a lot of land to cover.