Printable View
I think I'm going to start calling it beta with the next cycle. I ran my last 2 Savage Worlds games with it without a hitch.
At this point, I'm looking for coverage from Mac/Linux users (especially with the updater), as well as all non 3.5E/4E rulesets.
Testing with nWOD is great.
Thanks,
JPG
JPG - Both the latest Web Installer and standard updater tool, appear to be working well with CrossOver 10.2 under Mac OSX 10.7.3. (Not sure what happened the first time I ran the new updater but the paths issue seems to be resolved - existing app directory and app data folders are correctly found).Quote:
Originally Posted by moon_wizard
Some minor comments:
- when launched the Standard Installer immediately launches into an update whereas the WebInstaller does not.
- Notes - the Notes banner tab and first entry in the Notes windowlist is being rendered 2-3 pixels below the top of the scroll (instead of being immediately below) - this creates an ugly gap which is not present in the other campaign window lists.
- The campaign Encounter window list will not accept the drop of a reference Skill Challenge.
- Under Mac/CrossOver - Maximising the FGII desktop window to Full Screen and then returning to windowed mode results in the top bar of the X window containing FGII and (sometimes) the bottom half of the hotkeys to disappear. This results in no controls to close the window.
- Metal theme is missing my black versions of the NPC power attack symbols and some other graphics (I presume these were not included due to concerns surrounding IP infringement?) - If so I'll update the Metal Pro theme extension for 2.9
I accidently ran the updater in my unregistered version (on a WinXP Virtual Machine) and downgraded it to 2.8.1
Now I can't see to get it back to 2.9 at all - I've tried the Web Installler and Upgrade Link (both linked earlier in this thread) as well as just downloading it fresh and reinstalling.
Every tool I try keeps giving me the "setProcessDPIAware cannot be found in User32.dll" error, which sounds like the multi-touch handling bug which was fixed.
Can I be a pain and ask for a step-by-step guide on getting FG 2.9 (alpha) unregistered installed on a fresh XP machine (SP3 with DirectX 9 pre-installed - that was my problem last time).
-PW-
Oberoten,
I just found the portrait selection script error. I had to create a new campaign before it showed up.
DrZ,
* The Notes banner graphic was 2 pixels bigger for some reason. I'll clip it.
* Will look into skill challenge drop
* Not sure what is going on with maximize/restore in Crossover. FG sets the window style to restore the standard window frame when restored from full screen (same code as 2.8.1)
* For the Metal Pro theme, perhaps we can ask community what they prefer for the other graphics. It would be nice to have a single theme, so that you don't need to maintain extension.
Phantomwhale,
Run the web installer download in first post. Since you are running without command line parameters that FG adds, it should not start automatically. Choose Settings and make sure you are configured for Test mode. If it automatically starts updating for some reason, click Cancel quickly, then check your settings.
The web installer/updater determines whether FG is installed depending on whether the FantasyGrounds.exe application is located in the FG2 app directory. So, worst case, uninstall (or delete/rename main app), then run web installer.
Regards,
JPG
Moon_Wizard, I was talking to some of my players last weekend in one of my 4E games on syncing up the shown die rolls on the server and clients. I had several players suggest there be an option that all client chat window sizes be locked to the same size as the host's chat window on the understanding that this would usually mean everyone would see the same roll. The players in that game cared more about everyone seeing the same rolls show up on the dice than having a individually re-sizable chat windows.
After your improvements to the chat window, does having everyone with the same size chat window make it more likely everyone in the group will see the same number on a throw die? And if so would it be possible add an option to slave chat window size on the clients to the master in 2.9? I was thinking the Host would resize the chat window on his machine and then after the players all told him it fit on their FG desktop the host would just lock the size and forget it until someone new joined the group with a smaller screen size.
Theoretically, the dice results should be the same on the host and client machine as long as the dice positions, initial vectors and table boundaries are the same. That is what the original developers used as their assumption, as the rest is just physics modelling. There might be some corner cases by platform, but generally these are the controlling factors. With the addition of a resizable chat window, the table boundaries can vary, which I believe is causing most of the issues.
I have actually been considering whether to pass the table boundary information with each roll (to match the chat window size of the dice thrower), instead of trying to synch/lock chat window sizes. It seems like it would be a similar amount of work, but it would be a better experience.
Cheers,
JPG
setprocessDPIAware error during update?
That's what I reported only 4 posts ago (look up :)) - maybe your looking for the same solution (3 posts up - although I haven't had time to try it myself yet). If you have a different setup, or followed different steps, then I'd add more info here so that moon_wizard can better assist.Quote:
Originally Posted by KhybersGhost
Interesting, that would explain why I couldn't find it either !Quote:
Originally Posted by moon_wizard
Let me know if I need a code change in SWEX - I'm doing a bunch of stuff for SW Deluxe compatibility at the moment, so will be looking at a new mini-release to accompany 2.9 going live anyhow.
I am going to pull the SetProcessDPIAware function, since I don't think it actually changed anything. The original reason is to make sure that the updater scaled with different DPI settings, but it doesn't seem to be affecting anything when I change my DPI settings. I figured that leaving it in wouldn't hurt, but I guess it did. ;)
JPG