758df315a1
working ivshmem setup
2024-12-01 22:08:11 -05:00
7a6ef52144
ivshmem work
2024-12-01 19:24:43 -05:00
11766f6385
clean up nvfbclibrary more
2024-12-01 01:39:48 -05:00
599472a176
agent-vs2022/ -> agent/
2024-11-30 04:01:03 -05:00
c6ce36e2f0
Add README
2024-11-30 04:00:17 -05:00
af557a0dba
Make vs2022 path shared
2024-11-30 03:54:47 -05:00
26fca2525c
rename capture interface
2024-11-30 01:24:50 -05:00
3521879ced
Clean up NvFBC interfaces
2024-11-30 01:03:26 -05:00
80190c40af
remove old agent sources
2024-11-30 00:40:49 -05:00
182266ec3c
agent built with clang + vs2022 libs
...
a better compiler. also i dont need a seperate dev machine with vs 2013 installed anymore, thank god
2024-11-30 00:40:18 -05:00
e0e78a92e9
switch protocol a bit
...
a frame is now
[N tiles]
then the whole framebuffer
not great for bandwidth, but it's tolerable enough and the performance of it is vastly better.
at some point we can use ivshmem to sidestep that and just make it a cpu->cpu copy I guess
2024-11-27 22:15:36 -05:00
9e1e9ddf02
fix nvfbc sdk header for correct windows.h casing
2024-11-27 21:59:20 -05:00
f0b8310822
dont need to init twice
2024-11-24 13:25:45 -05:00
d185b0e855
retapped
2024-11-23 21:46:39 -05:00
c373de1571
warnings SUCK
2024-11-23 21:31:15 -05:00
2f2114aca3
retappingly
2024-11-23 21:30:39 -05:00
c1bb08c31f
agent: LARGE cleanup
...
interfaces are like a good thing.
2024-11-23 21:29:59 -05:00
4a37a97fee
fixed agent gitignore
2024-11-23 11:52:13 -05:00
5f9f547db8
clang-format
2024-11-20 21:29:22 -05:00
e10261543f
add agent source code
2024-11-20 21:26:35 -05:00
a5336349b8
tiles
2024-11-20 21:17:44 -05:00
0ed63eefa2
init
2024-11-20 18:44:18 -05:00
