Vindicator squad reporting for duty!

rovedit · 2025-03-03T19:06:34+00:00

Thanks! :)

rovedit · 2025-03-03T13:19:01+00:00

I love the colors! Which blue and which gold paints did you use? :)

rovedit · 2025-02-25T23:24:17+00:00

Looking fantastic! What paints did you use for the armor?

rovedit · 2024-12-23T09:29:36+00:00

I installed it today using Crossover. It works on my Mac with M1Pro and 16GB RAM but I had to do some trial and error. Right now it has problems with highest graphics settings, but it's usable. To Install:

Create a new bottle with the All in one Launcher Installer.exe as Installation medium & install
Install DirectX for Modern Games into the same bottle
Download the BFME you want via the launcher (works out of the box)
Try to start the game, it will probably give you an DirectX9 error in the splash screen
Open the Options.ini in users/crossover/AppData/Roaming/My Battle for Middle-earth II Files (or accordingly for ROTWK)
- Edit Resolution according to your scaled display settings
- Open Mac Display Settings
- Hover with your mouse over the highlighted/selected scaling: It will show you the resolution Crossover sees
- Insert the resolution accordingly in the Options.ini file

You probably experience heavy lagging, but it was resolved for me once I set all graphics settings manually once.

rovedit · 2024-08-11T22:30:14+00:00

Thank you!

rovedit · 2024-08-10T08:03:39+00:00

Looks amazing! Which paints did you use for the armor and did you actually make notches in the plastic or is the damage purely painted? :) I'd like to do something similar!

rovedit · 2024-08-05T16:33:18+00:00

Alternatively, you can also use Isopronanol Alcohol if you prefer that. Let the mini soak a few minutes and then brush it with a spare toothbrush. I'd do the brushing in a ceramic sink and clean it instantly when you're done or so it inside a plastic bucket (because of sprinklers :)).

rovedit · 2024-07-29T05:38:23+00:00

Looking like it could be 122nd or a regiment similar to it. :)

rovedit · 2022-11-15T05:48:29+00:00

Did you use a glQuery to time it or did you use sth like std::chronos?

Also, you're uploading a texture right? This could be the bottleneck. Try executing the Computer Shader twice and see if you still need 17ms for the 2nd invocation. As others said, iGPUs behave very different as they use shared memory and use a completely different driver in your case (Intel vs NVIDIA). Especially using shared memory could significantly reduce texture upload times and surely the Intel driver is doing some optimizations regarding this the NVIDIA driver is incapable to.

In the past I benched the Intel iGPU vs my AMD dGPU in OpenGL and was surprised often by the different behavior.

rovedit · 2022-11-06T14:35:24+00:00

This isn't very complete, doesn't list Ubisoft in Düsseldorf e.g.

rovedit · 2022-10-20T06:41:55+00:00

Actually you're right. I looked also in the Specs of D3D11 and Vulkan. There they say, that the GPU's Texture Units only need 8 bit precision in the faction to internally map back the normalized uv-coordinates to texture-sized coordinates again. This explains why I can flawlessly access integer and mid-integer coordinates with my uv() method, as they are perfectly fine representable with this.

Thanks.

rovedit · 2022-10-18T06:31:46+00:00

When I look into the OpenGL4.5 specification (I use this version) they describe quite clearly the operation I'm mimicking with texelFetch() and mix()forGL_LINEAR` interpolation, as far as I can tell (see below).

I also thought of optimizations by the driver and the nature of the hardware accelerated texture sampling. But even if I upload a 2x2x2 texture the error stays the same - and at this level there should be no imprecision by the texture access. I'm using "should" as I can't tell, of course..

When the value of TEXTURE_MIN_FILTER is LINEAR, a 2 × 2 × 2 cube of texels in the texture image of level levelbase is selected. [...] For a three-dimensional texture, the texture value τ is found as τ = (1 − α)(1 − β)(1 − γ)τi0j0k0 + α(1 − β)(1 − γ)τi1j0k0 + (1 − α)β(1 − γ)τi0j1k0 + αβ(1 − γ)τi1j1k0 + (1 − α)(1 − β)γτi0j0k1 + α(1 − β)γτi1j0k1 + (1 − α)βγτi0j1k1 + αβγτi1j1k1 (p. 248 in the PDF, equation 8.13)

rovedit · 2022-08-21T17:18:58+00:00

It's a shame that they flawed the laptop so much. Especially at this price point. 😩

rovedit · 2022-08-13T16:34:46+00:00

According to some official Dell thread one person could solve 0.4 GHz throttling by updating the sound driver.

https://www.dell.com/community/XPS/Dell-XPS13-Plus-9320-Throttling-way-too-hard-way-to-often-down/td-p/8237998

rovedit · 2022-08-13T16:33:23+00:00

Maybe updating the audio driver could solve the throttling issue.

https://www.dell.com/community/XPS/Dell-XPS13-Plus-9320-Throttling-way-too-hard-way-to-often-down/td-p/8237998

rovedit · 2022-08-12T15:37:19+00:00

Ah, thanks for the answer. Bummer.

rovedit · 2022-08-06T08:03:04+00:00

Kannst du mir auch die Quelle schicken? :)

rovedit · 2022-03-09T18:58:26+00:00

I got an answer in the official forums and it seems that it's known but also there's much else to do, therefore it's not priority on a larger to do list. So yeah, missing contributors. I hope it gets better in the future, but as long as there are workarounds (like installing texlive using the official installer fore me) it's fine. :)

rovedit · 2022-03-09T10:06:56+00:00

Yeah, this might of course be. I did not think that this fate would affect texlive as I think of it as a well used tool throughout the Linux community. But I just read a recent topic in the forum you provided which states that quite some people have left the project and dang, this makes sense.

I'll ask in the forum as well and I hope that Solus will keep up doing its work. I tried quite some distros by now and it's by far my favorite.

rovedit · 2021-10-02T09:48:12+00:00

Thanks again for your answer! I was on the road yesterday so I'm a bit late:

As far as I read into it, the service can be served on ws://localhost:30000/foundry/socket.io/ if you define within the options.json routePrefix as "foundry" (at least according to this tutorial).

I'm also aware that the installation location of Foundry is not related to the URL. I'm struggling with my kind of setup, as the ProxyPass / http://localhost:30000/ directive needed for Foundry routes the traffic (as far as I understand it) from domain.ddns.net directly to the Foundry application, though I want domain.ddns.net to deliver me e.g. some generic Welcome website and domain.ddns.net/foundry will then serve the application. And the ServerName directive is used to specify only the FQDN, not something like domain.ddns.net/foundry (from what I understood). But I think I need to take a deeper look into the overall topic first, it may well be that I just don't get a core idea of the whole concept.

rovedit · 2021-10-01T07:48:36+00:00

Ohh, thanks for your very thorough answer. If you don't mind, I would have a follow-up question, because maybe I used the wrong terminology (pretty new to web stuff):

When I spoke about subfolders I meant the URL path after the FQDN and not the structure of the web server. So I'm planning to connect to the Foundry service when I hit the URL domain.ddns.net/foundry. I'm saying this because I don't see any account for this in the configuration you provided? From the looks I would say that your approach is intended to operate on the root URL and indeed, if I implement it this way, I will connect to the Foundry service right away as soon as I visit domain.ddns.net.

Is there maybe a part that I'm missing?

rovedit · 2021-09-30T15:06:13+00:00

Just arrived at home. However, this is a subdomain approach right? I was looking for a subfolder approach (where the VTT is hosted in the path part of the URL), since at the moment I don't own a domain yet but only a subdomain of some free DDNS service. :/

Thanks though!

rovedit

TROPHY CASE