Jump to content

autofire372

New Member
  • Posts

    8
  • Joined

  • Last visited

Reputation

0 Neutral

About autofire372

  • Birthday 03/10/1991

General

  • Gender
    Male

Recent Profile Visitors

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

  1. Under Wine-staging 10.11, the bug where PKHeX breaks if its window is moved seems to have been fixed. Unfortunately, the following bug is now preventing me from opening the Trainer Info editor for any generation: Exception Details: System.Globalization.CultureNotFoundException: Culture is not supported. (Parameter 'name') en-us-posix is an invalid culture identifier. This seems to be a Wine regression, as the same versions of PKHeX work just fine on Windows 10. UPDATE: I am now convinced that this is a deeper problem with my desktop's primary Wine prefix, as switching to a different prefix alleviated all issues running PKHeX in Wine. UPDATE #2: It was definitely a Wine prefix issue; deleting and re-creating the prefix (and reinstalling .NET Desktop 9.0) fixed it. UPDATE #3: Didn't feel like double-posting. @Taku86 have you had an issue where Unicode characters (such as the nickname field) are cut off at the bottom?
  2. Might be a Wine regression, then. I just tried downgrading from .NET 9.0.3 to 9.0.2, and PKHeX was still bugged. EDIT: On second thought, downgrading wine-staging to 10.2 didn't fix the issue, either, so I dunno... EDIT #2: I just tried using KDE Plasma with Wayland in a virtual machine, and PKHeX was still broken. Maybe something is weird in my PKHeX settings... EDIT THE THIRD: Finally got PKHeX to behave correctly. I had to open winecfg and disable "Allow the window manager to control the windows" under the Graphics tab.
  3. Is anyone else experiencing an issue where PKHeX stops working properly if its window is moved elsewhere on the desktop? Using Wine 10.3 Staging with .NET 9.0.3.
  4. The following exception occurred in the DataGridView: System.ArgumentException: DataGridViewComboBoxCell value is not valid. To replace this default dialog please handle the DataError event. This message pops up when attempting to change tabs in the Underground Editor. It comes pretty close to spin-locking PKHeX, as it pops up again immediately after it is closed, ad infinitum. Hammering the OK button is needed to escape the error loop. Tested on Windows 10.
  5. Exception Details: System.FormatException: Format string can be only "G", "g", "X", "x", "F", "f", "D" or "d". at System.Enum.TryFormatPrimitiveNonDefault[TUnderlying,TStorage](RuntimeType enumType, TUnderlying value, Span`1 destination, Int32& charsWritten, ReadOnlySpan`1 format) at System.Runtime.CompilerServices.DefaultInterpolatedStringHandler.AppendFormatted[T](T value, String format) at PKHeX.WinForms.SAV_Misc4.ReadPoketch(SAV4Sinnoh s) at PKHeX.WinForms.SAV_Misc4.ReadMain() at PKHeX.WinForms.SAV_Misc4..ctor(SAV4 sav) at PKHeX.WinForms.Controls.SAVEditor.B_OpenMiscEditor_Click(Object sender, EventArgs e) Loaded Assemblies: -------------------- PKHeX, Version=23.12.23.0, Culture=neutral, PublicKeyToken=null Z:\home\****\Documents\pkhex\PKHeX.dll -------------------- User Message: An unhandled exception has occurred. You can continue running PKHeX, but please report this error. I first ran into this error in Wine, but it does reproduce on Windows 10 proper. This only happens when editing a Diamond, Pearl, or Platinum save; HGSS have no such issues.
  6. autofire372

    PKHeX on Linux

    Welp, the .NET 8 update broke PKHeX in Wine, as it now relies on a user32 function that is straight up unimplemented in wine. PKHeX_Error_Report 20231207142033.txt
  7. Figured it out - for some reason, the actual move flags for gen 6 are the unlabeled F17 to F32 flags; the labeled flags appear to be unrelated data.
  8. I can't seem to edit any of the move flags in any gen 6 game. They don't update scrolling through the move list, either. I tested with X and Omega Ruby. None of this happens with gen7, though (tested with Pokémon Sun).
×
×
  • Create New...