Author Topic: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread  (Read 91369 times)

Geiger

  • Guru of Life Emeritus
  • Chronopolitan (+300)
  • *
  • Posts: 315
    • View Profile
    • Geiger's Crypt
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #90 on: July 23, 2008, 09:10:33 am »
Just post a new thread here in Kajar.

Zakyrus

  • Entity
  • Magical Dreamer (+1250)
  • *
  • Posts: 1359
  • "Bouncy, bouncy, bouncy... --!!"
    • View Profile
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #91 on: August 14, 2008, 05:15:53 pm »
Could you add a display/text field in the treasure chest editor? One that it displays which memory address is used by the treasure being placed/edited. This may be useful for various purposes.

Edit:

I know I ask alot, could you add Layer mode(s) for the location map editor that shows only the "Sprite Over L1" & "Sprite Over L2" properties. (Simular to that of the Solidity, Battle Solidity, or Z-Plane layer modes) It's really irritating to have to right-click each individual tile to see those respective properties to make sure that they will layer over/under the Sprites accordingly. This feature shouldn't take too terribly long to code and it would save us mappers hours of annoyance.

Thanks a million.
« Last Edit: August 18, 2008, 12:21:47 pm by Zakyrus »

justin3009

  • Fan Project Leader
  • God of War (+3000)
  • *
  • Posts: 3296
    • View Profile
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #92 on: October 25, 2008, 06:50:15 pm »
Not sure, but a suggestion I'd like to see in use is have the Dialogue in Temporal Flux have a different colored background if possible.  The dialogue blends in so well that it's sometimes incredibly hard to find what you're looking for.  Having a separate colored background would make it an easy find.

Chrono'99

  • Guru of Reason Emeritus
  • God of War (+3000)
  • *
  • Posts: 3605
    • View Profile
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #93 on: December 07, 2008, 05:43:39 am »
In TF 3.0, if you put a Destination command in a location event and have "Onto Tile = False" and "Onto Object = False", it will still display "Destination(OnTile, OnObj)". And if you put the command and have one of the two values True (or both), TF will crash with this message:

Code: [Select]
System.OverflowException: Value was either too large or too small for an unsigned byte.
   at System.Decimal.ToByte(Decimal value)
   at System.Decimal.op_Explicit(Decimal value)
   at Temporal_Flux.LocEventEditorForm.OnUpdateCommand(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Chrono'99

  • Guru of Reason Emeritus
  • God of War (+3000)
  • *
  • Posts: 3605
    • View Profile
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #94 on: December 09, 2008, 04:18:37 am »
If you click on a heading in the Strings window to sort the Location names by "String", "Length" or "Compressed", the order of the location names will also change in the OW Exit menu, but not their actual values, which makes OW Exit selection difficult.

Agent 12

  • Zurvan Surfer (+2500)
  • *
  • Posts: 2572
    • View Profile
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #95 on: December 11, 2008, 10:25:22 pm »
When Clicking on some DrawGeometry Command you get a LogAssert:

Repro:

Open Fresh CT Rom
Open Location Event packet 105
Go to Object 12 Startup/Idle
Click on the DrawGeometry

--JP

Actually this is worse than I thought I can't seem to do any draw geometry commands
« Last Edit: December 11, 2008, 10:37:56 pm by jsondag2 »

Geiger

  • Guru of Life Emeritus
  • Chronopolitan (+300)
  • *
  • Posts: 315
    • View Profile
    • Geiger's Crypt
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #96 on: December 12, 2008, 09:35:41 am »
When Clicking on some DrawGeometry Command you get a LogAssert:

Please provide the error message next time.  I don't need the whole stack trace, just the first line will do.

"System.ArgumentOutOfRangeException: Value of '327' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'."

Also, line numbers are more helpful than objects/functions.

Vehek

  • Errare Explorer (+1500)
  • *
  • Posts: 1761
    • View Profile
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #97 on: December 27, 2008, 03:08:25 am »
Ever since TF 2.75, the Decode all events option doesn't seem to handle dialog correctly. Dialog is either blank or from the event packet Decode all was called from.

Zakyrus

  • Entity
  • Magical Dreamer (+1250)
  • *
  • Posts: 1359
  • "Bouncy, bouncy, bouncy... --!!"
    • View Profile
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #98 on: January 06, 2009, 03:52:49 pm »
TF 3.0:

File>Import:: Location Exits

Anything you try to import, exit value changes to "0"

~Z

Chrono'99

  • Guru of Reason Emeritus
  • God of War (+3000)
  • *
  • Posts: 3605
    • View Profile
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #99 on: January 06, 2009, 07:16:06 pm »
TF 3.0:

File>Import:: Location Exits

Anything you try to import, exit value changes to "0"

~Z

Doesn't it import ALL exits at once (same for export)?

Geiger

  • Guru of Life Emeritus
  • Chronopolitan (+300)
  • *
  • Posts: 315
    • View Profile
    • Geiger's Crypt
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #100 on: January 07, 2009, 09:26:59 am »
Doesn't it import ALL exits at once (same for export)?

Yes.  Same for treasure, as they are both Sized By Address record types.

justin3009

  • Fan Project Leader
  • God of War (+3000)
  • *
  • Posts: 3296
    • View Profile
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #101 on: January 09, 2009, 06:06:45 pm »
There's a bug that if you try to do "Epoch (in Party)", it'll automatically make it a return command, but "always" works fine.

Mauron

  • Guru of Reason Emeritus
  • Errare Explorer (+1500)
  • *
  • Posts: 1774
  • Nu-chan
    • View Profile
    • Maurtopia
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #102 on: March 12, 2009, 11:43:33 pm »
Would it be possible to add the six letter names patch through the patches option? The reason I ask is because ZeaLitY mentioned elsewhere that the dialogue handler could potentially clip longer lines if the names get extended.

The patch uses the same memory addresses for names, and the relevant routines were all edited without relocating code.

FaustWolf

  • Guru of Time Emeritus
  • Arbiter (+8000)
  • *
  • Posts: 8972
  • Fan Power Advocate
    • View Profile
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #103 on: March 13, 2009, 12:19:16 am »
Speaking of the sixth letter name patch, what's the possibility of doing the same for the seventh letter name patch currently in production?

Geiger

  • Guru of Life Emeritus
  • Chronopolitan (+300)
  • *
  • Posts: 315
    • View Profile
    • Geiger's Crypt
Re: Perpetual Temporal Flux Bug Report / Feature Suggestion Thread
« Reply #104 on: March 13, 2009, 09:19:16 am »
Speaking of the sixth letter name patch, what's the possibility of doing the same for the seventh letter name patch currently in production?

While the patches are certainly impressive, its unlikely that I will add any patches that change memory addresses of vital data.  It requires far too much code juggling.