Recent content by mrianura

for scailing 100$/100k sprites, but as there are a lot of AI development You can give a try to scale it Yourself, but thats not as easy at it seems. 3 years ago i spent over 2 months to train/improve my AI model and to implement postprocessing fixing some glitches. 1713997178 the main idea...

nice, I'm glad that You like my feature :D

const Rect screenRect(dest + (textureOffset - m_displacement *2 - (m_size.toPoint() - Point(1)) * g_gameConfig.getSpriteSize()) * g_drawPool.getScaleFactor(), textureRect.size() * g_drawPool.getScaleFactor()); m_displacement *2 should be everywhere

these 4, basically everywhere You have m_displacement You should multiple this by scale factor (64x64 means scale 2)

You can have a look at otcv8 changes, which I've made some time ago (regarding 64x64 sprites - HD mod) - filter otcv8 repo by mrianura author 1711468774 I solved there exactly Your issues

So in order to see cmake changes you have to regenerate msvc project (cmake-gui can be helpful). You can not use already provided project, because is not configured to use cmake.

what are You using to build the project ? MSVC project or cmake :D ?

I believe that's not much more work than one week ~30hrs of work. Basically You have to inherit Platform and window class. Even more - I saw a few years ago, that someone on this forum showed working otclient in web assembly.

Im I missing something ? Author asked for WASM otclient compilation, not to rewrite everything from scratch. As You can see, even Kondrah started this (not finished ofc), by adding new SDL window.

check if this path is valid -DLUA_INCLUDE_DIR=/opt/homebrew/Cellar/[email protected]/5.1.5_8/include/lua5.1/

@lexus21 bumped this, so i answered

Thats obvious, he forgot to inherit from LuaObject

for 10$ I would not even invest my time to write pm to You :D

You specified, that only null can cause segv, which is not true :)

pointer, which points to freed memory can cause segmentation fault :)