Jump to content


Photo

NearInfinity


  • Please log in to reply
1029 replies to this topic

#1021 Mike1072

Mike1072
  • Member
  • 538 posts

Posted 07 October 2020 - 12:33 AM

I made a mistake. I downloaded the newest GitHub version of NearInfinity NearInfinity-20200901.zip as I wanted to try the new functionality.

Now I cannot see the GUI even if I open my old 2019 jar file. I normally see everything in large size with dark background and light text because these are the only settings I can use to read text due to my vision. All I "see" of it is dark background with black text, or light background with light grey text, which are both totally illegible for me.

I have tried uninstalling and reinstalling Java and selecting menu options from memory inside the program. Ironically, with the new version of Java 8 I can now see things I couldn't before on the Java installation splash screens and such, but I cannot use the jar application to do anything besides open it in WIndows Explorer.

I realize this would not be a high development priority to fix for most, but would someone please help me to get the GUI to where everything is dark background with light text? Right now I can't even see to make different selections for the colors.


Are you on Windows 10?  It has an ability to invert all colours on your display (toggleable with a keyboard shortcut).  More details here: https://support.micr...e-color-filters

 

Edit: I think the default appearance is pretty standard dark text on a light background.  Here's what it looks like for me, at 100% text size using the "Metal" Look and Feel: https://i.imgur.com/rmoqoGx.png

 

If you're seeing something vastly different there may be something else going on.


Edited by Mike1072, 07 October 2020 - 12:40 AM.


#1022 Argent77

Argent77
  • Staff
  • 1137 posts

Posted 07 October 2020 - 08:16 AM

I made a mistake. I downloaded the newest GitHub version of NearInfinity NearInfinity-20200901.zip as I wanted to try the new functionality.

Now I cannot see the GUI even if I open my old 2019 jar file. I normally see everything in large size with dark background and light text because these are the only settings I can use to read text due to my vision. All I "see" of it is dark background with black text, or light background with light grey text, which are both totally illegible for me.

I have tried uninstalling and reinstalling Java and selecting menu options from memory inside the program. Ironically, with the new version of Java 8 I can now see things I couldn't before on the Java installation splash screens and such, but I cannot use the jar application to do anything besides open it in WIndows Explorer.

I realize this would not be a high development priority to fix for most, but would someone please help me to get the GUI to where everything is dark background with light text? Right now I can't even see to make different selections for the colors.


Near Infinity itself doesn't provide many options to change visual appearance. There is an option to change UI schemes (menu Options > Look & Feel), but I think the default UI scheme (Metal) is still the cleanest of all.

 

There is also a way to change the global font size to a percentage value compared to normal font size (see menu Options > Change Global Font Size).

 

If you have trouble accessing these options, I have attached a zip file containing several registry files which will change global font size for you, if you want to try them out: Attached File  ni_fontsize_options.zip   1.72K   46 downloads

 

Unpack the archive and double-click on a registry file (confirm the message dialogs, if there are any). Afterwards start Near Infinity. They provide 125, 150, 200, 250 and 300 percent increased font size compared to standard. It works best with the default UI, but may also work with a few selected other UI schemes.

 

Apart from that, Mike's suggestions to make use of Windows' "Ease of Access" features might also help.



#1023 Gamemacik

Gamemacik
  • Member
  • 12 posts

Posted 02 December 2020 - 06:42 AM

Hi, cut and paste function in NearInfinity-2.1-20200901 is completely broken.

 

How to reproduce bug.
 
Edit file "SCRL1X.ITM"
1. right click and cut "Item ability 0"
2. paste "Item ability 0" below "Item ability 1"
3. save and close file
4. reopen file ... :doh:
 

Spoiler


Edited by Gamemacik, 02 December 2020 - 06:57 AM.


#1024 Argent77

Argent77
  • Staff
  • 1137 posts

Posted 02 December 2020 - 08:07 AM

Hi, cut and paste function in NearInfinity-2.1-20200901 is completely broken.
 
How to reproduce bug.
 
Edit file "SCRL1X.ITM"
1. right click and cut "Item ability 0"
2. paste "Item ability 0" below "Item ability 1"
3. save and close file
4. reopen file ...

I can confirm this issue. It also applies to SPL resources with nested substructures. I'll see what I can do.



#1025 Argent77

Argent77
  • Staff
  • 1137 posts

Posted 23 January 2021 - 05:03 AM

Update: NearInfinity v2.1-20210123

Changelog:

  • Fixed ITM/SPL file corruption when appending Ability structures
  • Added EEex support (thanks Bubb)
  • Added option to sort IDS entries (found under "Format..." button > "Sort entries")
  • Show a game selection dialog if game is not detected automatically by NI
  • Improved handling of dialog.tlk when it's blocked by a running game
  • Updated various effect opcodes
  • Made list of available opcodes more game-specific
  • EFF V2.0: added more bits to "Dispel/Resist" field
  • EFF V2.0: changed "Dispel/Resist" field from list to flags
  • Improved save type flags descriptions
  • Internal fixes and optimizations


#1026 The Imp

The Imp

    Not good, see EVIL is better. You'll LIVE.

  • Member
  • 5064 posts

Posted 23 January 2021 - 05:38 AM

Changelog:

  • Added EEex support (thanks Bubb)
  • ...
  • Updated various effect opcodes

I am detecting a pattern here, now question is; How is this handled in a case where things don't crosspolynate ? ... aka, say the current game has no EEex installed, is the EEex info shown, and not exclusively separated to not be in effect without the EEex install. As it can lead to operational misleads.


Yep, Jarno Mikkola. my Mega Mod FAQ. Use of the BWS, and how to use it(scroll down that post a bit). 
OK, desert dweller, welcome to the sanity, you are free to search for the limit, it's out there, we drew it in the sand. Ouh, actually it was still snow then.. but anyways.


#1027 Argent77

Argent77
  • Staff
  • 1137 posts

Posted 23 January 2021 - 06:02 AM

EEex is handled just like TobEx. New opcodes are only available if EEex is detected. Changes to existing opcodes are handled in the same way as TobEx or game-specific differences. All of these changes are backwards compatible with vanilla game resources. So if you don't have EEex installed you'll just see some numbers in unused or differently labeled resource fields.



#1028 subtledoctor

subtledoctor
  • Member
  • 644 posts

Posted 24 March 2021 - 03:33 PM

Quick note: my mods use a function from... someone (Ardanis?) to create new spellstates in the next available slot of splstate.ids. That file in the unmodded EEs is filled to 118, so the function starts there. In BG2EE v2.5.16, my mod adds a spellstate at 119. Then 120 through 126 are already full, so the next spellstate the mod adds is 127.

 

When I look at the 318/326 effects of spells in NI, it shows "119 - DETECT_INVISIBLE" instead of the name of my custom spellstate. I assume that is because on some other games, slot #119 is filled with that state. So NI defaults to showing that. But in this case it is incorrect. Looking at the IDS file shows the correct name, but looking inside spell effects shows the wrong name.

 

This is just a cosmetic issue, to be sure - the only trouble it caused was making me think it was a bug on my end and losing 30 minutes trying to chase it down. But I thought I should drop a note about it.  Cheers!



#1029 Argent77

Argent77
  • Staff
  • 1137 posts

Posted 25 March 2021 - 01:39 AM

Quick note: my mods use a function from... someone (Ardanis?) to create new spellstates in the next available slot of splstate.ids. That file in the unmodded EEs is filled to 118, so the function starts there. In BG2EE v2.5.16, my mod adds a spellstate at 119. Then 120 through 126 are already full, so the next spellstate the mod adds is 127.

 

When I look at the 318/326 effects of spells in NI, it shows "119 - DETECT_INVISIBLE" instead of the name of my custom spellstate. I assume that is because on some other games, slot #119 is filled with that state. So NI defaults to showing that. But in this case it is incorrect. Looking at the IDS file shows the correct name, but looking inside spell effects shows the wrong name.

 

This is just a cosmetic issue, to be sure - the only trouble it caused was making me think it was a bug on my end and losing 30 minutes trying to chase it down. But I thought I should drop a note about it.  Cheers!


There are no hardcoded parts involved in showing the list of SPLSTATE entries. If you see an entry with a different name than you expected it's likely that there is a duplicate entry in SPLSTATE.IDS with that name.



#1030 Argent77

Argent77
  • Staff
  • 1137 posts

Posted 09 April 2021 - 11:39 AM

A quick preview of what can be expected in the next Near Infinity release:

This year Near Infinity will turn 20 years old. For that reason I'm working on a new feature of a similar scale (coding-wise) as the Area Viewer or the BAM Converter that will be ready for the next release. I'll provide more details about it later.

In addition to the new feature you can expect a great number of fixes and improvements for the area viewer, BAM converter, effect opcodes and various resource types.

I plan to release the next version shortly after the official release of the EE game patch 2.6 to make sure that it works reliably with the new patch, but probably not later than May (whatever comes first).