![]() ![]() The command will be in the cmd history in future if you need it, so you don't have to type it in every time. The model should be spinning right in front of the viewer after this command is entered. This will take you to the Mortar model on the map `erbium` (the pickup location of the mortar), so you can see issue. Once in the game, access the console and enter: This launches Xonotic and loads the game map `erbium` (a default map included in 0.8.2), which contains the mortar model. Once set up, run Xonotic with the cmdline options of `+map erbium` (eg. You probably want to run the game and set the graphics resolution and so on to match your display. I recommend installing this from the default download from as it avoids any possible issues with packaged versions. It has all the necessary maps and the affected weapon models. To reproduce this in Xonotic, you can use the following commands without connecting to a server: Have confirmed that the exact same model/setup renders on non-intel hardware (Radeon and Nvidia) using free and proprietary drivers. The Mortar model is the one that has the most consistent issue and therefore easily replicated. Just before 0.8.2 was released, some weapon models were updated to a new look, and it's only the new models which seem to have issues. Have noticed that the first frame always renders, then only the transparent part of the weapon renders (the sights) thereafter. I've done a few apitraces on this previously. I've been meaning to log this bug for a while (since ~17.0) but haven't had time or a suitable environment to do a proper investigation (and MESA builds).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |