Package Base Details: latencyflex-git

Git Clone URL: https://aur.archlinux.org/latencyflex-git.git (read-only, click to copy)
Submitter: ishitatsuyuki
Maintainer: ishitatsuyuki
Last Packager: ishitatsuyuki
Votes: 1
Popularity: 0.000134
First Submitted: 2022-01-03 02:38 (UTC)
Last Updated: 2023-03-19 10:15 (UTC)

Latest Comments

1 2 3 Next › Last »

ishitatsuyuki commented on 2023-04-16 08:25 (UTC)

Updated the source to use its own definition of those macros so this should work fine now.

hydrocryo01 commented on 2023-04-13 02:47 (UTC) (edited on 2023-04-13 02:47 (UTC) by hydrocryo01)

I got an error about VK_LAYER_EXPORT does not name a type during compilation:

In file included from ../latencyflex_ue4_hook.cpp:19:
../latencyflex_layer.h:26:12: error: ‘VK_LAYER_EXPORT’ does not name a type
   26 | extern "C" VK_LAYER_EXPORT void lfx_WaitAndBeginFrame();
      |            ^~~~~~~~~~~~~~~
../latencyflex_layer.h:27:12: error: ‘VK_LAYER_EXPORT’ does not name a type
   27 | extern "C" VK_LAYER_EXPORT void lfx_SetTargetFrameTime(uint64_t target_frame_time);
      |            ^~~~~~~~~~~~~~~
../latencyflex_ue4_hook.cpp: In function ‘void {anonymous}::lfx_FEngineLoop_Tick(void*)’:
../latencyflex_ue4_hook.cpp:27:3: error: ‘lfx_WaitAndBeginFrame’ was not declared in this scope
   27 |   lfx_WaitAndBeginFrame();
      |   ^~~~~~~~~~~~~~~~~~~~~

Do I miss something?

ishitatsuyuki commented on 2023-04-13 00:39 (UTC)

Please note that LatencyFleX 2 is in alpha development. Users should be aware of the caveats and the early access disclaimer should not be skipped.

Zeioth commented on 2023-04-12 23:41 (UTC)

I've made an alternative, easy to understand installer for LatencyFlex2: https://github.com/Zeioth/LatencyFlex2-installer

ishitatsuyuki commented on 2023-03-24 01:41 (UTC)

Cmon, don't flag a package just because it doesn't build. Flagging is only for cases where the version needs a bump.

Anyway, the same issue have been posted before, I don't know why, but make sure you have stock wine installed in your PATH. Most people with issues seemed to have some kind of custom wine.

Zeioth commented on 2023-03-24 00:39 (UTC)

It is still not building correctly for me:

FAILED: latencyflex_layer.so 
wineg++  -o latencyflex_layer.so latencyflex_layer.so.p/unixlib.cpp.o -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,--start-group -Wl,-soname,latencyflex_layer.so -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS /home/zeioth/.cache/paru/clone/latencyflex-git/src/LatencyFleX/layer/wine/../build/liblatencyflex_layer.so -Wl,--end-group
/usr/bin/ld: cannot find -ladvapi32: No such file or directory
/usr/bin/ld: cannot find -luser32: No such file or directory
/usr/bin/ld: cannot find -lwinecrt0: No such file or directory
/usr/bin/ld: cannot find -lkernel32: No such file or directory
/usr/bin/ld: cannot find -lntdll: No such file or directory
collect2: error: ld returned 1 exit status
winegcc: /usr/bin/g++ failed
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'latencyflex-git-r61.0470806-1': 
error: packages failed to build: latencyflex-git-r61.0470806-1

SunRed commented on 2023-03-20 00:54 (UTC)

Please add options=('!lto') to the PKGBUILD as it doesn't build with LTO enabled.

ishitatsuyuki commented on 2023-03-19 10:16 (UTC)

Guys, sorry for the delay. The submodule incompatibility has been fixed now (thanks TheBill2001).

Hsky commented on 2023-03-19 01:21 (UTC)

Newest upload doesn't work because of the new git update that changes how the -C argument works but changing git -C layer/subprojects/funchook submodule update distorm --> git -c protocol.file.allow=always -C layer/subprojects/funchook submodule update distorm on line 36 of the PKGBUILD allows me to build the package successfully

IncredibleLaser commented on 2023-02-28 07:27 (UTC)

The proposed solution is also the new official decision, the bug report has been closed with reference to the wiki that describes exactly what has been done in the latest comment. It'd be great if you could incorporate the suggested changes.

1 2 3 Next › Last »