ModelContextProtocol

L

Lyris the KitoriOP•6/29/23, 10:12 PM

transparent geometry when

A

Aqua•6/29/23, 10:12 PM

and opaque too

A

Aqua•6/29/23, 10:13 PM

when drawing opaque you should sort from front to back

LLyris the Kitori you also sometimes have to do the same in 3d in some ways

L

Lasek•6/29/23, 10:13 PM

Eeeeee okeey

L

Lyris the KitoriOP•6/29/23, 10:13 PM

you dont have to do that as much with only opaque if you properly have a depth buffer

A

Aqua•6/29/23, 10:13 PM

yea its not essential

L

Lyris the KitoriOP•6/29/23, 10:13 PM

but sorting beforehand does help with z-fighting (sometimes)

A

Aqua•6/29/23, 10:13 PM

it just means the gpu doesnt try to render fragments that will never be visible

L

Lyris the KitoriOP•6/29/23, 10:14 PM

yeah for performance you should sort opaque front to back

L

Lyris the KitoriOP•6/29/23, 10:14 PM

and transparent back to front

A

Aqua•6/29/23, 10:14 PM

although how much performance that gains over the cost of sorting on the cpu i have no idea

A

Aqua•6/29/23, 10:14 PM

ye

L

Lyris the KitoriOP•6/29/23, 10:14 PM

my solution for 3d rendering is to draw all my opaque geometry in one pass front to back, then all my transparent geometry after, back to front, should handle all cases

L

Lasek•6/29/23, 10:14 PM

hymmmmmm okey, my conclusion is: computer graphics are hard

L

Lyris the KitoriOP•6/29/23, 10:14 PM

but not the most performant solution

A

Aqua•6/29/23, 10:15 PM

thats what i do as well

L

Lasek•6/29/23, 10:15 PM

(I know nothing new)

L

Lasek•6/29/23, 10:15 PM

Anyway, thank you guys

L

Lyris the KitoriOP•6/29/23, 10:15 PM

np

A

Aqua•6/29/23, 10:20 PM

bruh filian was actually on ltt lmao

L

Lyris the KitoriOP•6/29/23, 10:20 PM

yea i saw that

K

Kai•6/30/23, 12:15 AM

yo @baebey, you know a bit of rust? Is there a zig packaging solution? Got a ~1700 loc of WASM Spec stuff now, and would love to share w/ the community somehow + have a good way to reference that myself

K

Kai•6/30/23, 12:15 AM

Rust cause anything like cargo/crates?

K

Kai•6/30/23, 12:15 AM

(but really irrelevant to the question I noticed)

L

Lyris the KitoriOP•6/30/23, 12:15 AM

wdym specifically by packaging solution, you want a package to be consumed by a package manager?

K

Kai•6/30/23, 12:16 AM

I guess?

L

Lyris the KitoriOP•6/30/23, 12:16 AM

if so: zig has a builtin package manager, heres how to create a lib which can be consumed through it https://github.com/InKryption/zig-pm-example-lib/tree/main

GitHub

GitHub - InKryption/zig-pm-example-lib

Contribute to InKryption/zig-pm-example-lib development by creating an account on GitHub.

K

Kai•6/30/23, 12:24 AM

thx

K

Kai•6/30/23, 1:02 AM

@baebey Hope I'm not bothering you, but what the fuck do I do now

zig test Debug native: error: thread 2227356 panic: zig compiler bug: GenericPoison
Unable to dump stack trace: debug info stripped

zig test Debug native: error: thread 2227356 panic: zig compiler bug: GenericPoison
Unable to dump stack trace: debug info stripped

zig test Debug native: error: thread 2227356 panic: zig compiler bug: GenericPoison
Unable to dump stack trace: debug info stripped

zig test Debug native: error: thread 2227356 panic: zig compiler bug: GenericPoison
Unable to dump stack trace: debug info stripped

L

Lyris the KitoriOP•6/30/23, 1:09 AM

what the hell

L

Lyris the KitoriOP•6/30/23, 1:09 AM

generic poison?

K

Kai•6/30/23, 1:10 AM

yup

K

Kai•6/30/23, 1:10 AM

Not sure what the fuck I did

K

Kai•6/30/23, 1:10 AM

but the compiler has given up on me

L

Lyris the KitoriOP•6/30/23, 1:11 AM

what did you change that caused it

K

Kai•6/30/23, 1:11 AM

I wrote ~1000 loc and now tried testing it again

K

Kai•6/30/23, 1:11 AM

L

Lyris the KitoriOP•6/30/23, 1:12 AM

i

L

Lyris the KitoriOP•6/30/23, 1:12 AM

see

K

Kai•6/30/23, 1:12 AM

I have literally 0 idea what could do this

L

Lyris the KitoriOP•6/30/23, 1:12 AM

try updating compiler ig

K

Kai•6/30/23, 1:12 AM

I have an inkling that it's this

K

Kai•6/30/23, 1:12 AM

fn read_vector_allocating_pooled(comptime T: type, allocator: Allocator, instruction_pool: *InstructionPool, reader: anytype, comptime callback: fn (Allocator, *InstructionPool, anytype) anyerror!T) ![]T {
    const len = try read_u32(reader);
    const result = try allocator.alloc(T, len);
    for (result) |*element| {
        element.* = try callback(allocator, instruction_pool, reader);
    }
    return result;
}

fn read_vector_allocating_pooled(comptime T: type, allocator: Allocator, instruction_pool: *InstructionPool, reader: anytype, comptime callback: fn (Allocator, *InstructionPool, anytype) anyerror!T) ![]T {
    const len = try read_u32(reader);
    const result = try allocator.alloc(T, len);
    for (result) |*element| {
        element.* = try callback(allocator, instruction_pool, reader);
    }
    return result;
}

fn read_vector_allocating_pooled(comptime T: type, allocator: Allocator, instruction_pool: *InstructionPool, reader: anytype, comptime callback: fn (Allocator, *InstructionPool, anytype) anyerror!T) ![]T {
    const len = try read_u32(reader);
    const result = try allocator.alloc(T, len);
    for (result) |*element| {
        element.* = try callback(allocator, instruction_pool, reader);
    }
    return result;
}

fn read_vector_allocating_pooled(comptime T: type, allocator: Allocator, instruction_pool: *InstructionPool, reader: anytype, comptime callback: fn (Allocator, *InstructionPool, anytype) anyerror!T) ![]T {
    const len = try read_u32(reader);
    const result = try allocator.alloc(T, len);
    for (result) |*element| {
        element.* = try callback(allocator, instruction_pool, reader);
    }
    return result;
}

K

Kai•6/30/23, 1:12 AM

could it be that the

fn (...) ...

fn (...) ...

fn (...) ...

fn (...) ... syntax is fucked?

L

Lyris the KitoriOP•6/30/23, 1:12 AM

i doubt it, but maybe?

K

Kai•6/30/23, 1:14 AM

any clue on what I could do?

K

Kai•6/30/23, 1:14 AM

I wanted to run this

/home/kaij/justwasm-zig/zig-cache/o/3717970ebcce144641f210c8d2a6f188/build /usr/lib/zig/zig /home/kaij/justwasm-zig /home/kaij/justwasm-zig/zig-cache /home/kaij/.cache/zig test

/home/kaij/justwasm-zig/zig-cache/o/3717970ebcce144641f210c8d2a6f188/build /usr/lib/zig/zig /home/kaij/justwasm-zig /home/kaij/justwasm-zig/zig-cache /home/kaij/.cache/zig test

/home/kaij/justwasm-zig/zig-cache/o/3717970ebcce144641f210c8d2a6f188/build /usr/lib/zig/zig /home/kaij/justwasm-zig /home/kaij/justwasm-zig/zig-cache /home/kaij/.cache/zig test

/home/kaij/justwasm-zig/zig-cache/o/3717970ebcce144641f210c8d2a6f188/build /usr/lib/zig/zig /home/kaij/justwasm-zig /home/kaij/justwasm-zig/zig-cache /home/kaij/.cache/zig test

manually

K

Kai•6/30/23, 1:14 AM

but I just get 0.11.0-dev.3771+128fd7dd0u printed out

K

Kai•6/30/23, 1:14 AM

and then nothing

L

Lyris the KitoriOP•6/30/23, 1:15 AM

that version is a bit outdated

you also sometimes have to do the same in 3d in some ways

Similar Threads

Similar Threads

Similar Threads