engine

Required skills: Python

Difficulty: Easy

For the initial asset conversion, openage provides textual output to signal which stage of conversion has been reached. The output usually looks like this:

INFO [py] converting metadata
INFO [py] [0] palette
INFO [py] [1] empires.dat
INFO [py] Starting conversion...
INFO [py] Extracting Genie data...
INFO [py] Creating API-like ob

how to use unocss with next.js?

The fix for #3307 was done for GitRepository only. This bug tracks the rest of the repositories.

The sidebar for the API Docs in the dashapp has position: sticky. This works well for when the sidebar content fits onto the screen, but when it doesn't it doesn't scroll independently from the main content (like it does for the Encore docs or the API Docs on app.encore.dev). So for when the main content is large (> 50000 px for us at the moment), you have to scroll all the way down to be able t

System Information

• Ogre Version: e80555d6a06dbcad192286818113ad69618b04a1
• Operating System / Platform: andr

Describe the bug
In Linux when the engine loads, it detects that there is EFX capabilities but then states that EAX 2 is out of the question.

Expected behavior
shoudln't EAX usage be replaced by EFX usage? and if so maybe this should be indicated when the sound is loaded, isn't it?

BugTrap error report

SOUND: OpenAL: enumerate devices...
SOUND: OpenAL: EnumerationExtensi

RulesEngine has many amazing features but lacks detailed documentation on those.

• Json based rules defination
• Multiple input support
• Dynamic object input support
• C# Expression support
• Extending expression via custom class/type injection
• Scoped parameters
• Post rule execution actions

Please comment on which feature you feel needs more/improved documentation.