Progress? about xray-16 HOT 9 CLOSED

Not really. I'm currently busy with my personal stuff, gonna proceed with xray later.

from xray-16.

I've mostly dropped contributing due to time constrains (I'm working on another project right now, plus I've got work on top of that). But other than that, I think it's just hit a little bit of a slow period.

from xray-16.

Slowly working on Luabind and LuaJIT update. Rebased on latest master branch.

from xray-16.

If somebody is still interested in it, I've made:

1. Rewritten cpuid to be asm-independent. (not copy-pasted SoC commit, as in CoP there are some new things which cpuid.cpp has to retrieve, such as affinity mask and stuff like this).
2. Implemented detection of Wine.
3. Rewritten some Blackbox code.
4. Rewritten everything, related to stacktrace. Now there is no more awful mix of asm and c++ from 2003 which was working correctly in 20% of cases.
5. Applied some optimizations and crash fixes to engine.
   However, I used @avoitishin fork, not exactly this repo, so I can't contribute directly.

from xray-16.

Regarding debugging subsystem and cpu detection - I've already rewritten that in xray (there's no blackbox stuff there anymore) but haven't apply on xray-16 yet.
Another thing is that I don't see any forks of xray-16 in your profile - where are the changes you made?

from xray-16.

I'm interested) but I can't commit

Îòïðàâëåíî ñ iPhone

25 ìàðòà 2015 ã., â 21:33, Pavel Kovalenko [email protected] íàïèñàë(à):

Regarding debugging subsystem and cpu detection - I've already rewritten that in xray (there's no blackbox stuff there anymore) but haven't apply on xray-16 yet.
Another thing is that I don't see any forks of xray-16 in your profile - where are the changes you made?

—
Reply to this email directly or view it on GitHub.

from xray-16.

You can commit to your fork.

from xray-16.

Any progress guys? And what branch is up to date, I suppose editors_vs?

from xray-16.

I'm currently busy with my own stuff, xray is on hold. editors_vs was created for porting borland-dependent editor tools to vc++/c++cli/c# so one could easily build the engine with all included tools.
If you don't want to deal with editors, use master branch.

from xray-16.