Jump to content

Gijs-Jan

Development Team
  • Posts

    344
  • Joined

  • Last visited

  • Days Won

    10

Gijs-Jan last won the day on May 7

Gijs-Jan had the most liked content!

Reputation

37 Excellent

Converted

  • Biography
    Game developer enthusiast!

    M.Sc. Artificial Intelligence; Maastricht University
    Lead Developer / Owner of CodePoKE.
  • Location
    Maastricht, Netherlands

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Can you download several saves, to ensure that if for any reason the steam setup is changed while we are trying to fix it; you still have them?
  2. Hey, looking through this seems to be mostly LLM analysis on stacktraces. Very interesting to see where things are going wrong (I might update the github wiki https://github.com/GoldhawkInteractive/X2-Modding/wiki) . Are there specific things you think that would help you?
  3. PDB is actually intentionally released to make modding of the game easier! The Moq DLL we'll take a look at.
  4. Thank you for the write up, and excellent to hear you enjoyed it!
  5. The error code mentions Win32 IO returned 112 -> Meaning that there was not enough space.
  6. We are keeping an eye on them and fixing the issue is definitely planned for the AI rework pass.
  7. Thank you for the extensive testing! We've found two bugs so far that we've fixed: 1. The tiles that trigger the UFO full reveal were sometimes behind the LOS blocking tiles, and couldn't get triggered. 2. During night time missions, we were incorrectly checking whether a unit had enough light to seeing the UFO, so it would reveal at normal vision sometimes. We're looking into the last one you reported.
  8. @Skitso Could you post using the bug reporter zip? I've added several logs on this so I can scan back what position triggered the reveal. Once you see it happen can you press F11?
  9. As a check: you can load a certain save, looking at the UFO, and when loaded the UFO is not revealed? (and reliably) Could you give me that specific save?
  10. @MarcelBru I've had this issue recently as well on Linux (Arch & Mint). The problem is that the i386 version of various graphics drivers got removed from graphics packages upstream on various distros (iirc - check this; or it was something along the lines of it becoming optional). Photon tends to use i386 instead of x64. You'll want to opt-in to the i386 version of whatever distro packages you have, and reinstall your graphics drivers / ensure that the appropriate versions have been installed.
  11. Hey, could you maybe give examples where the LOS and the shooting mechanics are not giving you the same info? From my perspective they use the same logic and should be telling you the same thing, so any cases where it's not I consider something we need to fix
  12. Is this on 4.6.0 or 4.5.0? We just discovered a bug with the save loading in 4.6.0, using older saves and fixing it now.
  13. Thank you for the bug report! We had to remove some assets to finally fully fix the bald-soldier problem, which caused any GC-save to no longer be valid. I'm sorry for the inconvenience it caused but for this one we had no way but to remove the assets and cause this issue. Your save from before the GC should still be valid!
  14. Cheers for the repro case! It's been fixed and we hope to release a hotfix for it soon.
  15. Cheers, thanks for the save - I'll have this one fixed quickly!
×
×
  • Create New...