https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • c
    4 lines of gl code frying my brain lol..... they will not win, i shall conquer them.
  • c
    And I did. Now its just a matter of getting the 3d image to show.
  • c
    Doc called and explained that ct scans to me. He is setting me up to see a lung specialist. I wonder what this adventure in health will end up being.
  • f
    Best of luck
  • c
    appreciate it.
  • c
    Hows your project coming along?
  • f
    Yeah, not too bad, I've been looking at the Kha side of it more than the UI recently. My Uni exams are kind of lagging on, got a calc exam tomorrow, so I'm in this limbo where I'm not properly studying, but not properly working either. In about a week though I'll have totally finished all Uni stuff and I'll be able to go 100% on the project 🙂
  • c
    Sweet, not much longer then.. Good luck on the exam. Those things can be stressful.
  • f
    Yeah, cheers 🙂
  • b
    good luck guys 🙂
  • f
    Yay, one exam to go, algorithms next week. Getting the strangest issue with my worlbuilding tool (haxeui+kha). When I allocate 1000x1000 array that uses HxNoise with vanilla haxe, hxcpp is chill, when I do the same within Haxe UI + Kha, it crashes with a backtrace that includes hxcpp's GC and haxe UI (!?) - but get this right, when I round off the floats hxnoise generates, even to like 5 decimal places, it works fine.
  • f
    Weirdest error 🤨 Rounding works though so I'm happy haha
  • b
    Kha uses the generational GC I think. But this is odd.
  • f
    Yeah, I was quite puzzled
  • b
    Try it as pure minimal Kha sample, report to Robert? Sounds interesting.
  • f
    Not even sure why rounding hxnoise output works - do you know if rounded floats use less memory?
  • f
    Yeah maybe 🙂
  • b
    I don't know much about hxcpp or cpp in general. But hxnoise seems to be part of the equation.
  • b
    Float should always be 64b in Haxe. Unless you use some different type.
  • f
    Yeah. Oh, here's another thing I didn't mention - just plain Math.random always worked!
  • b
    Rounding or not... Can't imagine it doing something. Unless it goes through some boxing and unboxing on cpp.
  • f
    Really weird. I looked at HxNoise code, I don't think it does any allocations for just a lookup
  • f
    Mmh. Strange one. Anyway, I'm just moving on for now heh, trying to push forwards a bit
  • b
    As I happen to be struggling with a cpp GC crash on a Haxeui project as well (haxeui-openfl in my case), I'm curious to know anything else u discover. Any code besides the noise array, or is that it?
  • f
    That's mostly what I got it down to - I was originally doing a whole bunch of extra drawing, but I mostly removed that and it stilled crashed. Interesting that you're having this issue too 🤔 Also makes me think it might not be a Kha issue. I don't like really ambiguous bugs like this 🙄
  • f
    Are you doing any significant memory workload things? What causes your crash?
  • b
    In my case, it often crashes on a map iterator. Maps, and in particular Iterator on cpp is not great.
  • f
    Ah, that sounds even trickier to diagnose, yikes
  • b
    In particular, Iterator is just a typedef. So in cpp, this is dynamic and it uses reflection to check for hasNext and next field in the dynamic iterator object. If this happens a Lot or often enough, things can move around and trigger attempts to access addresses like 0xfffff... etc. In my case, the map size can change, so it makes things even worse.
  • f
    Wow, that sounds terrible
1...294295296...1687Latest