Welcome, Guest. Please login or register.

Author Topic: AmigaOS4.1 Update 5 Released  (Read 9601 times)

Description:

0 Members and 2 Guests are viewing this topic.

Offline itix

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 2380
    • Show all replies
Re: AmigaOS4.1 Update 5 Released
« on: August 17, 2012, 12:16:43 PM »
Quote from: Karlos;703968
Well, if two executables have the same name, the same environment settings will be used. This is not anticipated to be a major problem, but if it is, renaming one of the executables should work. Remember, the vast majority of Warp3D applications are games.


You could calculate md5sum from the executable. Now if executable is updated it will be detected automatically and user dont have to edit settings again if compatibility problems were fixed in a new version.
My Amigas: A500, Mac Mini and PowerBook
 

Offline itix

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 2380
    • Show all replies
Re: AmigaOS4.1 Update 5 Released
« Reply #1 on: August 17, 2012, 02:34:11 PM »
Quote from: Karlos;703977
Perhaps it wasn't clear, but the driver only ever reads environment vars, it never writes them. If an updated executable gets a new name and you want to keep the same settings, rename the subdirectory in ENVARC:Warp3D//

Tweaking shouldn't be that common since for the most part, the default settings are the correct ones. Notable exceptions are things like Wipeout2097, which depend on a number of incorrect behaviours of the legacy Permedia2 driver.

Many of the driver options are performance tweaks, for example, being able to turn redundant framebuffer clears into no-ops, using a narrow Z buffer and so on.


Ah, I see. I thought it would have automatically generated default settings for each Warp3D application you could edit from a preferences editor. It is clear now.
My Amigas: A500, Mac Mini and PowerBook