Back to multiplane overlays, I think. I can’t get resource sharing across context resets working reliably in D3D12 
Stuff happens in the wrong order, and then it’s a frozen black image forever.
I can see why Microsoft doesn’t bother trying to inject code directly into games with the game bar overlay.
I’m still dead set on removing CEGUI though. That’ll simplify rendering code and maybe native D3D12 will be easier when I gut that fish?
“Build it and they’ll come” and all of that I guess 
It’s an enormous help that Discourse can translate a copied selection from PCGW to Markdown, as it speeds it up the process as it allows me to get a good baseline for a page. Though after that I can often spend edit, rewrite, or restructure a page for quite some time before I find it “finished.”
Hell, just the Global injection page has some 28 revisions now between the two of us, and that’s just the number of times we’ve hit “Save” – the number of actual edits on each revision can be off the charts due to how good Wiki.js’ preview is.
Lol, having created even more pages on the wiki, I find us in the position where we probably have to consolidate information a bit as the main menu is already being pushed a bit too long for my taste.
Expandable menu sections are apparently planned for Wiki.js, but seemingly not finished yet.
Hmm… Gonna have to think about this one a bit.
@Kaldaien, something I noticed was how using the “PHP” codeblock format on the wiki colorizes the syntax in a good way:
```php
[Input.XInput]
Enable=false
Rehook=false
PlaceholderMask=0
UISlot=0
SlotReassignment=0,1,2,3
```
Before:
After:
It’s a bit weird though, because Discourse supports both that and the separate ini syntax highlighting, but neither creates the same result here on Discourse.
im new here.can i use special k mod on horizon zero dawn.thanks for help
To anyone who uses the text OSD in Special K, would it be acceptable if it were changed to draw a translucent background behind the text?
In other words, the OSD becomes a widget with a background…
I don’t see many other options for getting text to be legible if I switch to ImGui for rendering the OSD. It does not support the border / drop shadow that I am using in CEGUI to draw the OSD text.
Would it be possible to let us set the ARGB of the background? That way if we wanted it fully transparent, we could. If so, that’d be fine.
In regards to the wiki, I sorta threw in the towel in terms of having the “list of games compatible with Special K” here as the lack of sortable columns along with the lack of styling made the list a hassle to use.
I’m simply linking to the PCGW list for now instead.
XD, the base of both logos are octagons, so it’s normal for them to seem similar.
Aperture Science wants their logo back:
Soo, feedback on the logo?
Btw, imma just insert this here
Too simple, I guess? 
You can’t recreate something more similar to the current “SK” logo?
I’m deliberately going for simple, which is how all professional logos are. That logo you sent had the letters slapped on top awkwardly. The pixel look also won’t scale well at lower output resolutions. This is a better version of that same logo btw
On another note, the base of the wiki is almost finished now. The most important stuff from PCGW have been copied over and rephrased/rewritten/updated where I noticed was appropriate.
Some stuff remains to be moved over (e.g. keybindings, issues, config parameters, etc) which I’ll get to later – as well as in general attempt to further tidy the place up and restructure some pages and their sections (e.g. I want to divide Video Management into various ‘main’ categories like “Window management” etc).
Refined it just a little further. This actually maintains that “pixels” approach, it’s technically a combination of shapes i made from nine large pixels. If i darken it, it will probably look very similar to the older logos.
We’re talking about a SVG that will at worst be sized 34x34 – that look is fine for it. The key is to retain the same overall design across multiple services while also adhering to the various themes used.
For example, the reason why I mentioned that logo with the “SK” on it is because otherwise the icon ends up being half invisible against the background of the wiki:
So by using the “SK” logo we’d not only match Discourse but also Discord, ergo achieving a matching identity across all services.
And on that note, I ended up throwing the existing PNG at the wiki instead in the meanwhile.
