Update available (2.4.4)

[Goblin-King]

Version 2.4.4

Fixed an issue causing new characters in local mode to be uneditable.
Related to the above, fixed an issue causing problems with the Lite version local character loading.

[Sid1120]

My FG2 now crashed everytime I press one of the main launcher's button (Load campaign, New campaign, etc.).

Any way for me to give you additionnal info on my problem?

[Spyke]

It's working fine on my FG2, Sid1120 (XP service pack 3, GURPS or 3.5e). Could you let us know your machine details (Vista, 64 bit, ruleset, etc?). That would help the Devs.

Spyke

[Sid1120]

Should be XP 32bit pack2

[Griogre]

I had clients with 2.4.1 and 2.4.3 versions connect with a server running 2.4.4 today. You probably don't want different versioned clients to connect to the host server.

[Blue Haven]

WOW!! but you can have diferent versions connected to you?? i mean players with diferent versions? because before it wont let them connect...

[Goblin-King]

WOW!! but you can have diferent versions connected to you?? i mean players with diferent versions? because before it wont let them connect...
The first number in the version number is the major version, that won't change much.

The second is the minor, or compatibility version. If it is different, clients can't connect to the host, and it is usually updated when either the network protocols change or a major update occurs.

The last number is what we call the build number (although it doesn't exactly reflect that always), and typically fixes bugs that don't affect the interoperation of connected instances. If it is different, you can make connections, although non-updated versions naturally suffer from the issues fixed in the latest release.

[Function]

We all patched last night. We are using the newest 4e rule set from FUM. All running XP 32 bit as far as I know. We have a few issues but it didn't seem to crash more than usual.

1. Still can't mouse wheel on an external second monitor.
2. Some clients get alot of combat tracker scripting errors. (seems to be when new mobs are added to the tracker)
3. Have to close (with axe) and reopen combat tracker to see mobs that have become "visible".


These are the main errors we have noticed but I will try to flesh them out after our next session with error messages and such.

/function

[joshuha]

2 & 3 will have to be brought up with the ruleset maker on the FUM forums.

I read about 1 earlier and I think it has to do with directX and support for multi-monitors in FG. I think I head if you left it in windowed mode and stretched it across it might work? Or that someone had a thread where he had to install some alternate mouse drivers.

[Tenian]

I haven't been able to reproduce either 2 or 3

[Zeus]

Saturday Night 4E_JPG_CUSTOM ruleset /FGII 2.4.4/Vista 64bit/ KotS adventure. We played our first game in 6 months with zero errors/crashes.

- No client crashes when new maps + tokens shared
- Client attack/damage/effect drops on map with no issues
- No repeating <shortcut> recordname entries in modulesdb XML files

We played for 4.5 hours straight. Great fun.

Many thanks.

[Tenian]

Just ran my first full session with 2.4.4:

Module Tokens do save map positions correctly between sessions.

Module tokens do still cause clients to randomly crash when first made visible to the players (either by unmasking them or by toggling them to visible on the CT).

[Spassvogel42]

New Update killed my Fantasy Grounds in Windows 7. I get a popup that says "Fantasy Grounds II is not a valid WIN32 application.

[EugeneZ]

New Update killed my Fantasy Grounds in Windows 7. I get a popup that says "Fantasy Grounds II is not a valid WIN32 application.
I have been using FG2 on Win7 for some time now and haven't had any problems.

[Zoso]

Are you using 32 or 64 bit? I have been running the 64 bit build 7100 without any issues.

[EugeneZ]

32-bit here.