The Orx community is pleased to announce the 1.14 release.
There are quite a few changes in this release.
Here are some highlights:

• Bundle, a new extension that can automatically discover and pack all your game resources, either inside separate binary packages or directly within your game’s executable.
• The Bundle extension is very efficient: it performs much better than using a lot of separate small files, cf. https://discord.com/channels/522167736823185418/717482097207672843/1103761922215661749 .
• It also supports compression, encryption, filters and is fully customizable.
• Lot of work was made on the Android plugins and its build system.
• The latter has been completely revamped and should be working out-of-the-box in all cases.
• The core clock can now be prevented from going to sleep as a trade-off between CPU usage and the eradication of potential micro-stutters that could happen under some circumstances.
• Custom commands can now be run on spawned objects, thanks to the new Spawner config property OnSpawn.
• Build type (release, debug, profile), CPU, platform and other system properties can now be queried at runtime either through the config system or with a command.
• The config include directive now supports an optional condition.
• A ton of quality of life improvements and a handful of API/event refactoring.

The complete list of changes can be found here: https://github.com/orx/orx/blob/master/CHANGELOG .

One issue I have is that the resources are stored in .GFF files, which I'm able to extract the majority of. Now I would prefer to extract this data during runtime. So, I see some options:

1) Add a custom loader (like in orxAndroid_RegisterAPKResource()), and load from there. My concern is that some things may not translate correctly. For example the image data is stored as two different entries in the gff. A palette entry and then then a data entry. Naturally I have a routine that translates that combination into 24-bit RGB or 32-bit RGBA.
2) Load the data in C and not in .ini. In other words use orxObject_Create(), etc... to create the objects.
3) Explode all the data into .bmp/png files on disk and then load.

I prefer 1) as I have the backend for that and it would allow people to overlay any extensions/mods in the .ini/config files--which would be slick.

I'm not opposed to 2), but that seems to defeat the purpose of ORX since that would be ignoring the whole data-driven .ini/config.

I don't like 3) at all because that is just seems super lame to me. Also, I'd have copyrighted data exploded on disk as opposed to its original format. Additionally there are certain parts of the original engine that use alternating palettes to create effects, which I haven't thought of how I would implement that yet.

Naturally I'd love to hear opinions.

Specifically any direction on 1) to get me started? I can keep reading the code, but any direction/examples would be helpful. Preemptive apology if I missed where this was documented already.

am new here,
how do I make an visual editor to make it similiar to rpg maker GUI
or at least a rpg game on here?

How to reproduce:
1) turn off vsync
2) set frequency to 0 in the clock section (otherwise vsync = false will have no effect)
3) set a fixed physics framerate
3) start a game, any game
4) limit all cpu frequency to 500 MHz, and the framerate will drop significantly which is expected. What is unexpected is that object also moves significantly slower.
5) cancel the cpu freq limits, rerun the game, the framerate can easily exceeds 1000 fps on my device and my little hero becomes a flashman.

Since Orx is not a engine especially dedicated for some kind of console platform, I would say this should be a bug. I looked into the code (glfw, orxPhysics.cpp) and confirmed that the physics updating code intends to achieve fixed time step and I counted that the calling rate of b2world->step is correct, which means this part of code works fine. I also confirmed that orxSystem_GetTime gives correct results and main clock dt is correct. So I honestly got no clue, why would physical movements depend on main framerate?

The Orx community is pleased to announce the 1.13 release. There are a substantial amount of changes in this release. Some highlights include:

• 70+ updates or new features
• Added a new SoundSystem plugin based on MiniAudio: All platforms now support loading OGG, WAV & MP3 files as well as writing WAV files
• Support for: config-driven filters for both sounds and buses, multiple sound listeners, sound panning (including commands), sound spatialization (entirely revamped: is now data-driven & independent of the channel count)
• Support for the QOI image format to all plugins/platforms
• Support for position literals with optional offset
• Compressed texture/icon/cursor support for desktop versions using Basis Universal (UASTC -> ASTC/BC7)
• Added orxMod (ProTracker MOD) based on the pocketmod library, that adds config-driven MOD support to objects
• Added orxMovie (MPEG1/MP2) init extension, based on the PL_MPEG library
• Spawners with UseSelfAsParent will now detach spawned objects upon deletion
• Native arm64 support for MacOS 11/XCode 12.x
• Support for VS2022 and retired support for VS2015
• The complete list of changes is here: https://github.com/orx/orx/blob/master/CHANGELOG .

The Orx community is pleased to announce the 1.12 release. Some highlights include:

• Major speed & scalability improvements: from 65k to 16M concurrent objects in memory, a complete rewrite of the orxBANK module, object update re-write, added support for early exit events handling

• Support for joysticks on Android-Native

• A simpler Android build pipeline (can be entirely built from inside Android Studio without the manual NDK build step)

• Added color literals for all HTML web colors. Can be used for Object, Graphic & FX Color values

• Added Nuklear support for new projects with the init project maker tool

• Support for writing JPEG images

• Many smaller fixes/optimizations/improvements. Complete list of changes is here: https://github.com/orx/orx/blob/master/CHANGELOG

These are just a few aspects of the problem. ORX's config system is too free for non-trivial games where there could be thousands of sections weaving upon each other. If one mistyped just one word in a complicating config system, it would be a pain in the ass to find it out. More so if commands are abusively used in the config system, but I guess that would be another topic. I wonder if anyone feels the same about this, because I feel that even a tiny improvement can do me a lot of good given the current situation.

The engine and the config system are simple and effective and I think we would all like to keep it that way. So the task would be how to improve the robustness and scalability without introducing too much complicity. In my opinion, given that ORX is a data-driven engine, the responsibility of the config system is to correctly organize the data so that the engine can parse them as the user expected or throw errors if otherwise (while runtime variables and game logics should be kept in the code). To achieve this, we would need to set some rules for the data format.

For now, I've got some simple ideas but they might not be very complete at this moment.

First of all, enhancement of explicity.

1) Typed sections
ORX uses config section of free forms to create objects and structures. The engine does not know what a section represents until it is used to create structures. I think that maybe we can give a hint to the engine so that it can know what a section really is and perform checks. For example, we can write the title of a section like this:

[HeroObject:Object]

So that the engine would know that this section is a definition of an object. This way, the engine can throw a warning when a section name of incorrect type appears in where it shouldn't be. This done, the check of entries become possible. For when the type of a section is determined, the engine can query its type to get a list of internal entry names and restrictions on the values (these infomation should be registered on the init of the config module). This way the engine can throw a warning or an error when a neccessary entry is missing or a value is invalid.

2) Distinguish internal entries from external entries
Let's call the hardcoded entries as "internal entry" and the ones defined in the config files as "external entry". To make the data format even stricter, we can provide a way to explicitly specify an internal entry name for use in both assignment and reference. We might want this because sometimes missing an internal entry is not noticeable. To implement this, we can allow the user to choose to prefix an internal entry name with '~' when an internal entry is wanted, or to set a rule that the first letter must be uppercase for internal entry and lowercase for external entry. Actually I personally prefer the latter one for it doesn't need to define more symbols and can completely divide entries into two types. So it would be like this:

; Explicitly declaring HeroGraphic as a Graphic section
[HeroGraphic:Graphic]
; Assigning an internal entry (start with uppercase letter)
Texture = hero.png

; Inheriting a section makes it has both its original type and the type of the inherited section
; In this case maybe we can allow omitting the type of HeroGraphic1 and default it to parent section's type.
[HeroGraphic1:Graphic@HeroGraphic]
TextureSize = (64, 64)
TextureOrigin = (64, 0)

[HeroObject:Object]
Graphic = HeroGraphic1
; Defining & assigning an external entry (start with lowercase letter)
health = 100

This way, any typo or invalid assignment can be discovered at parsing phase (of course this does not apply when a value is a command string).

3) Redefinition of a section throws a warning
Currently, redefining a section defaults to extending the original one. I think it would be more helpful to have it the other way round. That is to say, the engine should throw a warning and wipe the old entries if a section is defined twice without a '+' prefix.

4) Handle collision flags and groups more safely
Typos in collision flags are hard to find out because collision flags are defined on a object section's instancing. Maybe we can have a special section to register all collision flags before using them. The same applies to group names as well. For now, one can mitigate these problems by using data inheritance. For collision flags there is one more thing to be addressed. Collision event might not be emitted if collision flags are not used in pairs. Collision pairs should also be pre-registered to ensure there's no broken pairs. It will look like this

[Collision]
Flags = hero # monster # wall # bullet
; Define collision pairs. All flags must be pre-defined in 'Flags' entry
; (hero <-> monster) and (hero <-> wall)
hero = monster # wall
; (bullet <-> monster) and (monster <-> wall)
monster = bullet # wall
; If there are flags not included in pairs, throw a warning

5) Settings sections are special
Forbid the definition of new (external) entries for settings sections. Forbid type hinting too. So this

[Console:Object]

and this

[Console]
ScrollSize = 1000
abc = 1

should result in errors. This way it doesn't change anything for using it but ensures nothing unexpected would happen when a special settings section is misused as a normal one.

Secondly, enhancement of section prototype design.
1) Section entries should be carefully designed so that coupling between the effects of different entries is diminished to an extreme extent. I propose this because I once encoutered confliction between different entries (although I can't recall exactly which section type and which entries).
2) If confliction can't be avoided, then the engine should check the potentially conflicting entries and their values and throw a warning if neccessary.

Thirdly, data scope.
Currently all sections are referenced by one linked list which allows no means to separate them. Maybe it would nice to have scopes in config systems just as in common programming languages. I'm not quite sure yet.

So, this is it. I would love to hear from the developers and other users. I haven't touch the code yet but would be happy to if this proposal sounds acceptable.

While you are at it, can you also point me to the list of supported image formats?

Thank you

New to the Orx Engine. I've compiled it using Visual Studio, I notice that by default Orx uses FASTCALL when exporting to DLL. Is there a way to change to that CDECL? Without having to change every FASTCALL name to CDECL?

I am trying to use the example iOS project, but the example doesn't seem to work. It builds just fine but crashes with a stack overflow error when run in the simulator. Near the top of the console log I see this error message

[36m[21:53:03][0m [31m[ASSERT][0m [35m[orxConfig.c:orxConfig_PushSection(5347)][0m [41m[37m[5mFAILED ASSERTION [orxFLAG_TEST(sstConfig.u32Flags, orxCONFIG_KU32_STATIC_FLAG_READY)][0m

When I update to the latest build it crashes with the same console log message and this stack trace

`0 0x0000000101057ff4 in _orxDebug_Break at /Users/orsonbushnell/Development/orx/code/src/debug/orxDebug.c:452

1 0x0000000101041556 in orxConfig_PushSection at /Users/orsonbushnell/Development/orx/code/src/core/orxConfig.c:5455

2 0x0000000100fe607a in -[orxView CreateBuffers] at /Users/orsonbushnell/Development/orx/code/plugins/Display/iOS/orxDisplay.m:817

3 0x0000000100fe47be in -[orxView initWithFrame:] at /Users/orsonbushnell/Development/orx/code/plugins/Display/iOS/orxDisplay.m:633

4 0x0000000100fe323c in -[orxViewController loadView] at /Users/orsonbushnell/Development/orx/code/plugins/Display/iOS/orxDisplay.m:435`

Can anyone tell me how to build for iOS?

[PlayerObjectFront@PlayerObject]
AnimationSet = PlayerAnimationSetFront
Position.z = > Object.GetPosition ^, > + < (0,0,0.1), Object.SetPosition <
IgnoreFromParent = position.position.z

Any suggestions on how to get this config to work?

As a side thought I was also hoping to make a server/client architecture in the future, and was wondering whether its a terrible idea tying things to animations in this case, and how much having the server not actually display the animations on the screen will affect its animation routine.

[22:12:20] [ANIM] [orxAnimSet.c:orxAnimSet_CreateSimpleAnimFromConfig(2283)] AnimSet [JamesAnimationSet]: Failed to create anim [RunAnim], couldn't create any frames.

My sprite sheet is 1840x256, the sprite size is 80x128, the first row is idle and second row is running animation.
It seems to work fine with the idle animation, and my "RunAnim" seems to semi-work if I set the RunAnim: TextureOrigin = (0,65), however anything above this it crashes even though its 256 pixels tall.

Is there something simple I'm missing here, I dont have any scaling or anything applied to the object. Any help is appreciated.

;###################################
; Player
[PlayerObject]
Graphic = PlayerGraphic
Position = (100,-100,0)
AnimationSet = JamesAnimationSet
Smoothing = true

[PlayerGraphic]
Texture = James.png
;Pivot = Center



; Animation
[JamesAnimationSet]
Texture         = James.png
FrameSize   = (80, 128, 0)
;Pivot      = center
KeyDuration     = 0.1
IdleAnim    = 23
RunAnim = 3
StartAnim   = IdleAnim
IdleAnim-> = IdleAnim # .RunAnim
RunAnim-> = RunAnim # .IdleAnim

[IdleAnim]
TextureOrigin = (0,0)

[RunAnim]
TextureOrigin = (0,128)

;###################################

I have defined the player physics like this:

[Player]
Position = (0, 0, 0)
Scale    = 1
AnimationSet = PlayerAnimationSet

[PlayerAnimationSet]
Texture = avion_sheet.png
FrameSize = (64, 64, 0)
PlayerIdle = 2
PlayerMoveFast = 2
StartAnim = PlayerIdle
Pivot = center
Body = PlayerBody

[PlayerBody]
PartList        = PlayerBodyPart
Dynamic         = false

[PlayerBodyPart]
Type            = box
Solid        = true
SelfFlags = hero
CheckMask = ufo

With [Physics] / ShowDebug at true, i don't see neither the physic debug shape, nor coordinates axis.

That's odd, because with simpler objects (ufos which have no animations, body defined in the object entry) , i can see the physic shapes.

[Ufo]
Graphic = UfoGraphic
Body = UfoBody
Pivot = center

[UfoBody]
PartList        = UfoBodyPart
Dynamic         = false

[UfoBodyPart]
Type            = sphere
Solid       = true
SelfFlags = ufo
CheckMask = ufo # hero

And it gives that:

I'm not sure where i should define Physics.
I tried to define Body in [Player] but with a box type, it raises an assert (no assert with sphere, strangely). Anyway, i see only coordinates axis in this case, not the debug shape.

Thank you for reading

I recently discovered ORX and I have a game idea I want to make reality. But... I am not that interested in C or C++ - but I do like the up and coming Nim language. I have worked a bit with Nim, making my own little language in it and some other utilities. I also know the creator and the Nim community fairly well - top notch and very sharp people.

So, since ORX is C99 and Nim integrates VERY well with C/C++ I have created a first shot at a wrapper. Nim compiles via C which means the calls to ORX have zero overhead. Nim also produces fast C code so there is seldom any real performance difference. However, Nim is a richer language while being much easier to program in. One can always take a peek at https://nim-by-example.github.io

If one wants to play with it, the best place to start is via my ORX clone at github. The wrapper lives in the subdirectory code/nim:

https://github.com/gokr/orx/tree/master/code/nim/norx

I will try to keep it in sync with the ORX master branch!

I develop on Linux but Nim is cross platform so it should be possible to use Norx on all platforms. There is just a silly port of the "spinning logo" so far, but the wrapper should in theory (modulo bugs of course) be complete because it was in most part autogenerated from the ORX headers. While using it I intend to "smooth things out" making it less "C" and more "Nim".

Any and all comments welcome!

regards, Göran

When I go to that website there is no orx-extern folder in https://bitbucket.org/orx.

Everything is fine when installing HEAD, but I don't want to rely on unreleased code for my game.

Can someone either release a 1.11.1 that points to a valid url, or restore the file to the url above?

Thank you

So is there a prescribed procedure for taking a game I worked on in visual studio on windows and getting it built on my mac? I quickly tried cloning down the repository to the mac but realized there is no mac build folder in the project. I don't want to do any authoring on the mac, just want to be able to build a finished game that was authored on windows. Any advice for how to best proceed?

thanks!

While I am tinkering with Orx, and formulating some ideas, I thought I would get to know a little about every one, and also share a little about myself.

So, just a quick post about when you started, your first language, and why you program.

I'll start:

I first thought about designing games back in '02 when some of my friends told me they would absolutely play my stories if they were made into games. So, in summer of '03, I bought Game Maker(which was pretty new at the time), and tinkered around with it for a couple of years. I hated it. I then bought DarkBASIC in '08(my first real programming language) after a 3 year hiatus. The language later went defunct in lieu of their App Game Kit.

I messed around with a number of langauges from 2010 to 2016 including Java, Javascript, HTML/CSS, Python, C#, F#, J#(pretty much every #), C, C++, FreeBASIC, QuickBASIC, QB64(a 64-bit QuickBASIC dialect), before returning to C++.
The reason I program is to push my limits, force my brain into different thought processes, and turn my ideas into functioning toys that people can play with.

Thank you for reading, and I hope to hear from everyone,
-Wolf

[Edited for ease of reading issues]

Thanks very much for any guidance. Here is a shot of the hint I'm seeing with the typo in it:

AINVAR Document syntax proposal
; [SectionName] - no modifications
;
; KeyName[FreeKeyName|PostFixedKeyName|Enum] = [[ValueType(limit):Default|None] | [[ValueType(limit):Default|None] & [ValueType(limit):Default|None]]:
;
; KeyName attributes:
;   FreeKeyName         = KeyName is a place holder for a list of free key names
;   PostFixedKeyName    = KeyName is a place holder for a list of free key names that will have KeyName as postfix
;   Enum                = Value of an existing enum known or defined in place. 
;                         Known enums are conveniently input keys (mouse/keyb/joy)
;                         Enums defined in place will follow *enum definition syntax*
;
; Value attributes:
; [[ValueType(limit|(min<max)):Default|None]
;
;   ValueType           = Int|UInt|Bool|Float|Vector|String 
;                           (min & max can be applied, if present. the interval can be open (min<) = min to infinite (<max) = -infinite to max)
;                         Enum
;                         Template:TemplateType
;                         List:Type:... ; In this case the (limit) value is used to express the max list size
;                         FilePath:DynamicLibrary|Storage|Config|Image|Sound
;                         DirectoryPath
;                         Command
;                         ShaderExtension
;
;   Default             = type default value, if appliable
;                         None that by default the key is not defined
;                         
;
; Since a key may have multiple value rapresentations, we can give a way to document such alternatives
; KeyName = [[typedef1] | [typedef1]] ; means we can have valuedef1 type or typedef2
; KeyName = [[typedef1] | [[typedef1] &# [typedef3]] ; means we can have valuedef1 type or typedef2 and typedef3 separated by #
;
;


; Enum definition syntax
; [Enum:name{value1|value2|value3|...}]
;
; In addition, to make the document more readable, I propose a special section used to declare enums and avoid in-place definitions
; [@EnumDefs@]
; EnumNameA = value1|value2|value3|...
; EnumNameB = value1|value2|value3|...

i'm looking for the most elegant way to manage game scenes ?

My first thought was to create a GameScene class and then create "MainMenuScene", "PlayScene" and "OptionsScene" classes and simply call current_scene.run() in my Run function.

But this solution felt ... hacky, so what's the official way to achieve this ?

Thanks

I'm facing a problem with this tutorial and it's torturing my mind.
link

I'm trying to make a title menu with two item "Play" & "Quit" highlighted when you hover with your cursor, exactly what's proposed with this tutorial. I understand that they are dynamically creating the animation name with the help of a prefix which is launched with a global AnimationSet linked to each button.

When I'm compiling no error is shown but when I'm launching the program it spits this:

[19:34:14] [CONFIG] [orxConfig.c:orxConfig_ProcessBuffer(2781)] [ASMRd.ini]: Begin include @ASMR.ini@
[19:34:14] [CONFIG] [orxConfig.c:orxConfig_ProcessBuffer(2781)] [ASMR.ini]: Begin include @Title.ini@
[19:34:14] [CONFIG] [orxConfig.c:orxConfig_ProcessBuffer(2787)] [ASMR.ini]: End include @Title.ini@
[19:34:14] [CONFIG] [orxConfig.c:orxConfig_ProcessBuffer(2781)] [ASMR.ini]: Begin include @Inputs.ini@
[19:34:14] [CONFIG] [orxConfig.c:orxConfig_ProcessBuffer(2787)] [ASMR.ini]: End include @Inputs.ini@
[19:34:14] [CONFIG] [orxConfig.c:orxConfig_ProcessBuffer(2781)] [ASMR.ini]: Begin include @Player.ini@
[19:34:14] [CONFIG] [orxConfig.c:orxConfig_ProcessBuffer(2787)] [ASMR.ini]: End include @Player.ini@
[19:34:14] [CONFIG] [orxConfig.c:orxConfig_ProcessBuffer(2781)] [ASMR.ini]: Begin include @Crosshair.ini@
[19:34:14] [CONFIG] [orxConfig.c:orxConfig_ProcessBuffer(2787)] [ASMR.ini]: End include @Crosshair.ini@
[19:34:14] [CONFIG] [orxConfig.c:orxConfig_ProcessBuffer(2781)] [ASMR.ini]: Begin include @Physics.ini@
[19:34:14] [CONFIG] [orxConfig.c:orxConfig_ProcessBuffer(2787)] [ASMR.ini]: End include @Physics.ini@
[19:34:14] [CONFIG] [orxConfig.c:orxConfig_ProcessBuffer(2787)] [ASMRd.ini]: End include @ASMR.ini@
[19:34:14] [CONFIG] [orxConfig.c:orxConfig_ProcessBuffer(2676)] [ASMRd.ini]: <Display.Title> = ASMR -> ASMR (Debug)
[19:34:14] [LOG] 
* This template project creates a simple scene
* You can play with the config parameters in ../data/config/ASMR.ini
* After changing them, relaunch the executable to see the changes.
[19:34:14] [DISPLAY] [orxGraphic.c:orxGraphic_CreateFromConfig(815)] Couldn't get text or texture for graphic (StartButtonInactive).
[19:34:14] [ANIM] [orxAnimSet.c:orxAnimSet_CreateSimpleAnimFromConfig(2241)] AnimSet [StartButtonAnimSet]: Failed to create anim [Inactive], couldn't retrieve associated texture's size.
[19:34:14] [DISPLAY] [orxGraphic.c:orxGraphic_CreateFromConfig(815)] Couldn't get text or texture for graphic (StartButtonActive).
[19:34:14] [ANIM] [orxAnimSet.c:orxAnimSet_CreateSimpleAnimFromConfig(2241)] AnimSet [StartButtonAnimSet]: Failed to create anim [Active], couldn't retrieve associated texture's size.
[19:34:14] [ANIM] [orxAnimSet.c:orxAnimSet_CreateSimpleFromConfig(2499)] AnimSet [StartButtonAnimSet]: Can't add link(s) starting from [Active]: source anim is missing.
[19:34:14] [ANIM] [orxAnimSet.c:orxAnimSet_CreateSimpleFromConfig(2499)] AnimSet [StartButtonAnimSet]: Can't add link(s) starting from [Inactive]: source anim is missing.
[19:34:14] [ANIM] [orxAnimPointer.c:orxAnimPointer_SetCurrentAnim(1070)] 0 is not a valid ID for the anim pointer.
[19:34:14] [ASSERT] [orxAnimSet.c:orxAnimSet_ComputeAnim(3438)] FAILED ASSERTION [_u32SrcAnim < orxAnimSet_GetAnimCount(_pstAnimSet)]
Illegal instruction (core dumped) 

My ini

[Button]
Group           = UI

[ButtonAnimSet]
KeyDuration     = 1
StartAnim       = Inactive
Inactive        = # 0
Active          = # 0
Inactive->      = Inactive # .Active
Active->        = Active # +.Inactive

[StartButton@Button]
Graphic         = StartButtonInactive1
AnimationSet    = StartButtonAnimSet
Position        = (0,50,-1)
Pivot           = center
Scale           = 1

[StartButtonAnimSet@ButtonAnimSet]
Prefix          = StartButton

[StartButtonInactive1]
Texture         = Ui/Start_Inactive.png
TextureOrigin   = (0,0,0)
TextureSize     = (256,256,0)

[StartButtonActive1]
Texture         = Ui/Start_Active.png
TextureOrigin   = (0,0,0)
TextureSize     = (256,256,0)

My Function called in orxUpdate

void _menuHover()
{
    orxOBJECT *currentObj;
    orxVECTOR cursorPos;
    if(orxRender_GetWorldPosition(orxMouse_GetPosition(&cursorPos),orxNULL,&cursorPos) != orxNULL)
    {
        currentObj = orxObject_Pick(&cursorPos,orxString_GetID("UI"));
    }
    
         if(currentObj != previousObj)
    {
        if(previousObj != orxNULL)
        {
            orxObject_SetTargetAnim(previousObj, orxNULL);
        }
        
                if(currentObj != orxNULL)
        {
            orxObject_SetTargetAnim(currentObj, "Active");
        }
        
        previousObj = currentObj;
    }
}

Finally don't know if it's relevant or not, I'm working on Ubuntu 20.04 and CodeLite.

I've tried lots of things and nothing worked, so any help is appreciated.

Thanks in advance.

[TileGraphicbeginning]
Texture    = "SnowSides.png"
Pivot  = top left
TextureSize    = (32,32,0)

[beginning0@TileGraphicbeginning]
TextureOrigin  = (0,0,0)

[beginning1@TileGraphicbeginning]
TextureOrigin  = (32,0,0)

[beginning2@TileGraphicbeginning]
TextureOrigin  = (64,0,0)

[beginning3@TileGraphicbeginning]
TextureOrigin  = (96,0,0)

[beginning4@TileGraphicbeginning]
TextureOrigin  = (128,0,0)

[beginning5@TileGraphicbeginning]
TextureOrigin  = (160,0,0)

[beginning6@TileGraphicbeginning]
TextureOrigin  = (192,0,0)

[beginning7@TileGraphicbeginning]
TextureOrigin  = (224,0,0)

[beginning8@TileGraphicbeginning]
TextureOrigin  = (256,0,0)

[beginning9@TileGraphicbeginning]
TextureOrigin  = (288,0,0)

[beginning10@TileGraphicbeginning]
TextureOrigin  = (0,32,0)

[beginning11@TileGraphicbeginning]
TextureOrigin  = (32,32,0)

[beginning12@TileGraphicbeginning]
TextureOrigin  = (64,32,0)

[beginning13@TileGraphicbeginning]
TextureOrigin  = (96,32,0)

[beginning14@TileGraphicbeginning]
TextureOrigin  = (128,32,0)

[beginning15@TileGraphicbeginning]
TextureOrigin  = (160,32,0)

[beginning16@TileGraphicbeginning]
TextureOrigin  = (192,32,0)

[beginning17@TileGraphicbeginning]
TextureOrigin  = (224,32,0)

[beginning18@TileGraphicbeginning]
TextureOrigin  = (256,32,0)

[beginning19@TileGraphicbeginning]
TextureOrigin  = (288,32,0)

[beginning20@TileGraphicbeginning]
TextureOrigin  = (0,64,0)

[beginning21@TileGraphicbeginning]
TextureOrigin  = (32,64,0)

[beginning22@TileGraphicbeginning]
TextureOrigin  = (64,64,0)

[beginning23@TileGraphicbeginning]
TextureOrigin  = (96,64,0)

[beginning24@TileGraphicbeginning]
TextureOrigin  = (128,64,0)

[beginning25@TileGraphicbeginning]
TextureOrigin  = (160,64,0)

[beginning26@TileGraphicbeginning]
TextureOrigin  = (192,64,0)

[beginning27@TileGraphicbeginning]
TextureOrigin  = (224,64,0)

[beginning28@TileGraphicbeginning]
TextureOrigin  = (256,64,0)

[beginning29@TileGraphicbeginning]
TextureOrigin  = (288,64,0)

[beginning30@TileGraphicbeginning]
TextureOrigin  = (0,96,0)

[beginning31@TileGraphicbeginning]
TextureOrigin  = (32,96,0)

[beginning32@TileGraphicbeginning]
TextureOrigin  = (64,96,0)

[beginning33@TileGraphicbeginning]
TextureOrigin  = (96,96,0)

[beginning34@TileGraphicbeginning]
TextureOrigin  = (128,96,0)

[beginning35@TileGraphicbeginning]
TextureOrigin  = (160,96,0)

[beginning36@TileGraphicbeginning]
TextureOrigin  = (192,96,0)

[beginning37@TileGraphicbeginning]
TextureOrigin  = (224,96,0)

[beginning38@TileGraphicbeginning]
TextureOrigin  = (256,96,0)

[beginning39@TileGraphicbeginning]
TextureOrigin  = (288,96,0)

[beginning40@TileGraphicbeginning]
TextureOrigin  = (0,128,0)

[beginning41@TileGraphicbeginning]
TextureOrigin  = (32,128,0)

[beginning42@TileGraphicbeginning]
TextureOrigin  = (64,128,0)

[beginning43@TileGraphicbeginning]
TextureOrigin  = (96,128,0)

[beginning44@TileGraphicbeginning]
TextureOrigin  = (128,128,0)

[beginning45@TileGraphicbeginning]
TextureOrigin  = (160,128,0)

[beginning46@TileGraphicbeginning]
TextureOrigin  = (192,128,0)

[beginning47@TileGraphicbeginning]
TextureOrigin  = (224,128,0)

[beginning48@TileGraphicbeginning]
TextureOrigin  = (256,128,0)

[beginning49@TileGraphicbeginning]
TextureOrigin  = (288,128,0)

[TilesMap]
Map    = beginning43 #beginning43 #beginning43 #beginning43 #beginning43 #beginning43 #beginning43 #beginning11 #beginning10 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 #beginning2 

1. All orx compiled programs accept the following parameters:

-c --config
-v --version
-h --help

If I wanted to re-purpose the -c parameter for something else, how could I do that? The tutorial here https://orx-project.org/wiki/en/tutorials/system/commandline_parameters only works for everything except the above default parameters.

2. If I wanted to test for other optional arguments passed, but not create handlers for them? How would I go about this. I assume all params are set using orxParam_SetArgs(argc, argv), but how could I access them? For example, if I wanted to test if the user specified an -x argument but I have no handler set up for it, how is that done? Standard c args tests perhaps?

3. Last case, if I have a handler for a parameter, and the argument is passed, the handler will execute. That much is good. But how did I test if the user did not pass the argument. Standard c testing code here as well?

It's very likely all my use cases above are intertwined. I can work around them but it would be cleaner if I can understand how to access anything collected by the orxParam module.

Some highlights include:

• Project build tool "Init" now supports the creation of orx/Scroll, Dear ImGui and orxArchive based projects.
• Support changes for MinGW-w64, including new support for 64bit, addition of Visual Studio 2019 and removal of VS2013
• OSX/Retina and Windows high DPI display issues corrected
• Control over polled physical peripherals.
• Text animations
• Object LifeTimes based on fx, sound, spawn, track and child, not just time.

There is a lot in this release. Check out the full list of changes at: https://github.com/orx/orx/blob/1.11/CHANGELOG

You can download the 1.11 release here: https://github.com/orx/orx/releases/tag/1.11
And to always stay up to date, the github version is at: https://github.com/orx/orx

An example using hp, where equipped_list and effects_list are keys on the object that are just lists of other sections that currently affect the character:

[StatSolver]
Equations  = StatEquations
Defaults   = StatDefaults
Update     = change

[StatDefaults]
base_hp      = 10
base_mult_hp = 1
damage_hp    = 0

[StatEquations]
max_hp                = Clamp(0, max_hp_cap, (base_hp * base_mult_hp) + (equipment_mod_hp * equipment_mod_mult_hp))
total_hp              = max_hp + (temporary_mod_hp * temporary_mod_mult_hp) - damage_hp
max_hp_cap            = infinity
equipment_mod_hp      = Sum(equipped_list, equip_modifier_hp, default: 0)
equipment_mod_mult_hp = Sum(equipped_list, equip_modifier_mult_hp, default: 0)
temporary_mod_hp      = Sum(effects_list, temp_modifier_hp, default: 0)
temporary_mod_mult_hp = Sum(effects_list, temp_modifier_mult_hp, default: 0)

This would, given any orx object, generate the attributes base_hp, base_mult_hp, damage_hp, total_hp, max_hp_cap, equipment_mod_hp, equipment_mod_mult_hp, temporary_mod_hp, and temporary_mod_mult_hp on that object.

I've currently got a parser and topological sort working, I've started on setting up a VM for it, but I noticed that the orxConfig API isn't thread safe, which I would need if I wanted to solve for multiple characters in parallel if the equations are referencing lists of config sections, but not if they're just referencing other variables on the object itself, since that can be saved to a hashtable beforehand. The only solutions I can think of so far are either manually doing mutex locks when reading the config (not ideal), duplicating the code from the config module to read values from another section without modifying the config section stack (also not ideal), or just dealing with solving for one object at a time (which limits how much it can be used). Just wondering if there's any tips on this.

I was wondering if there is any cool orx-config style way of doing camera lag in general. It can sometimes be a nice effect for certain kinds of games....I can imagine having a maximum velocity.x/y options for child objects that allow them to catch up to their parents rather that adopt their positions instantly. A max lag distance could also be set so that the child can't get more than a certain distance away from its parent position. I didn't see anything like this so far, so curious if there is already some way to do this that I'm not seeing (other than code it myself, which is fine).

thanks

https://ncase.me/sight-and-light/

For visualization, I'm using the orxDisplay_DrawPolygon function to see my light blocking polygons and also to fill in the resulting "light area" polygon. Since I can't use that function to fill a non-convex polygon, I'm just filling in a series of triangles that can be made from the rays and their endpoints. All working as expected.

My plan was to use the resulting polygon (or collection of triangles) to multiply onto a light map texture that contains my lights in order to create some simple shadows. What I can't figure out yet is how to draw the polygons somewhere other than the main display (ie, onto my light map texture). As far as I can tell, the DrawPolygon feature is tied to the current display, correct?

I'm probably missing the obvious, but what would be the suggested way to get the light polygon drawn onto a texture?

You can follow us on Twitter, Mastodon, Facebook, Google+

The wiki points to main .cpp which I used.

Within /ImGuiOrx/imgui/examples I find several main .cpp versions for a variety of APIs.

Regarding the high framerate at the beginning, some OpenGL drivers go into busy loops with VSync if VSync is requested too soon after the creation of a window. To prevent this, we request VSync only half a second after the window's creation.

I realize I am using the "GLFW + OpenGL2, using legacy fixed pipeline" which may account for those behaviors.

Which APIs does Orx support and which does igtest.cpp use?

I haven't done anything yet other than look over how the lighting tutorial works, but I have a general question about how to handle lights in a large map. So, the character light is easy because in my setup, the character is always at the center of the screen. I'd like to be able to place lanterns in the map to light up various areas. Of course, these light sources may or may not be on the visible part of the map. I think one way to do this is to look at any light sources in the world (these would probably be regular orx objects) and determine if their location is visible on the screen, and if so, update an array of available lights with the appropriate light color, position, radius, etc. This assumes a setup with a static array of lights similar to the tutorial approach. That would limit the number of lights in a scene to whatever size the array is, and would maybe require some prioritization if there are too many light sources in the scene.

Having never tried to do something like that, I'm wondering if that is a sound approach, or is there some more standard way of handling this that makes more sense. Any advice or suggestion is welcome.

Here is the parameter list, and I've set a default value for the new parameter HighlightAlpha

If in the shader if I use

color.a = 0.35;
it works fine,
but
color.a = HighlightAlpha;

makes the shader not work at all.

I also see when I try to set the parameter in code, that it doesn't like the float value

Not sure what I've done wrong here.

I don't think it is feasible to generate a bunch of orxOBJECTs for each block in the grid for performance reasons. I was thinking of keeping my world in a large 2d array of bytes, with the values representing what type of block is at that location. (1 = dirt, 2 = grass, 3 = rock , etc). For rendering, I'd loop through the visible portion of the array (dependent on player position) and render rectangles according to the values in the array. I've actually done something like that a few years back with my own home-grown stuff. Any hint as to how I could render out textures in Orx directly like that?

The other thing to handle would be collision. I feel like that also may require some custom collision handling rather than using the orx body. Since I'd know where the player is on the grid, I really only have to check a few of the values in the array that are near the player for collision. I know collision can be tricky, but think I can handle doing that part.

So, I'm curious if that sounds like a way to go, or if there are other well-known approaches? Probably the biggest unknown for me is how to render the textures directly without using orxOBJECTS (unless there is a workable approach using them)

thanks for any comment!

Any suggestion for how I can get those .h files to show as part of the project?

thanks

Thanks in advance.

Then anyone can download and have them printed and drop them around at game or developer conferences.