Exult Forum

Hello Everyone,
I have an interesting crash.
I am using Windows 10 Pro x64 build 1809.

Exult Studio installs fine however I cannot open any menu.
When a menu is opened the program displays a blank box and then crashes.
I've tried uninstalling and reinstalling a few times now.

Is anyone else having this problem?

Welcome.

I'm running Windows 10 Pro as well, having no problems, although system info says I'm at build 16299.

But of course it doesn't have to be Windows related, so hopefully someone knows what's up and can provide you with actual help.

Stupid question, but you are using the latest version available in the download section, right?

I have not run into this myself.

Looks like we may be mixing the Windows 10 Version number (4 digits) and the OS build number (5.3 digits). Using the start menu, "about" should give you the Settings window that has both "Windows specifications".

If you open the %appdata% location via the start menu, click Up to to the main AppData folder, then Local -> Exult, there should be studio_err.txt and studio_out.txt. That may help tell you what is wrong.

Thanks, KC.

@Grant: My version is 1709, not that your newer version is likely related to the problem. But never say never I guess, since it wouldn't be the first time one of their forced updates breaks something.

More info on Windows 10 versions, from MS:
https://docs.microsoft.com/en-us/window ... nformation

I've downloaded and run the installer from yesterday.
Just before I posted.

I am on version 1809 build 17763.253

studio_err has the following.
Warning, trailing slash in path: "\"
Warning, trailing slash in path: "\"
Line 140 doesn't start with a number
Error opening temporary file in gamedat dir with port number.
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\static\map01\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\patch\map01\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\static\map02\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\patch\map02\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\static\map03\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\patch\map03\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\static\map04\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\patch\map04\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\static\map05\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\patch\map05\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\static\map06\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\patch\map06\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\static\map07\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\patch\map07\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\static\map08\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\patch\map08\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\static\map09\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\patch\map09\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\static\map0a\"
Warning, trailing slash in path: "D:\Programs\Origin Systems\Ultima7\patch\map0a\"

and studio_out has
Looking for 'blackgate' at 'D:\Programs\Origin Systems\Ultima7'... found game with identity 'FORGE'
Looking for 'forgeofvirtue' at './forgeofvirtue'... but it wasn't there.
Looking for 'serpentisle' at 'D:\Programs\Origin Systems\Serpent'... found game with identity 'SILVER SEED'
Looking for 'silverseed' at './silverseed'... but it wasn't there.
Looking for 'serpentbeta' at './serpentbeta'... but it wasn't there.
Black Gate : not found (\.)
Forge of Virtue : found
exult_bg.flx : found
Serpent Isle : not found (\.)
Silver Seed : found
exult_si.flx : found


Do either of these logs help at all?

Can you copy/paste the exult.cfg and the other stdout/stderr txt files?
It might be a problem with permissions or the many map numbers (why is that btw?)

Exult.cfg





D:\Programs\Origin Systems\Ultima7


(default)


sqsfxbg.flx




D:\Programs\Origin Systems\Serpent


(default)




1




yes



yes


gs




yes


gm



yes


0




yes


0



1.0000


yes


MT32Emu


yes




yes



no


22050


yes




yes


no


no


yes


no


no


no


no



0


normal


original


no



8


double


yes


100


no


no


no


yes


-1


1




3


Hq3x


no


no



1.00


1.00


1.00





0


0


0



0


0




960


720



Aspect Correct Centre


Bilinear


yes


5




no


No


yes




blackgate


gimp




Stdout
Exult version 1.5.0git
Built at: Nov 27 2018 20:11:18
Compile-time options: USE_FMOPL_MIDI, USE_MT32EMU_MIDI, USE_EXULTSTUDIO, HAVE_ZIP_SUPPORT
Compiler: gcc, version: 4.6.2

Platform: Windows Unknown NT Version 6.2 Build 9200
Exult path settings:
Data : data
Digital music : data\music

Looking for 'blackgate' at 'D:\Programs\Origin Systems\Ultima7'... found game with identity 'FORGE'
Looking for 'forgeofvirtue' at './forgeofvirtue'... but it wasn't there.
Looking for 'serpentisle' at 'D:\Programs\Origin Systems\Serpent'... found game with identity 'SILVER SEED'
Looking for 'silverseed' at './silverseed'... but it wasn't there.
Looking for 'serpentbeta' at './serpentbeta'... but it wasn't there.
Black Gate : not found (\.)
Forge of Virtue : found
exult_bg.flx : found
Serpent Isle : not found (\.)
Silver Seed : found
exult_si.flx : found
Checking rendering support
Windowed
640x480 8 bpp ok 16 bpp ok 32 bpp ok
720x480 8 bpp ok 16 bpp ok 32 bpp ok
720x576 8 bpp ok 16 bpp ok 32 bpp ok
800x600 8 bpp ok 16 bpp ok 32 bpp ok
1024x768 8 bpp ok 16 bpp ok 32 bpp ok
1152x864 8 bpp ok 16 bpp ok 32 bpp ok
1176x664 8 bpp ok 16 bpp ok 32 bpp ok
1280x720 8 bpp ok 16 bpp ok 32 bpp ok
1280x768 8 bpp ok 16 bpp ok 32 bpp ok
1280x800 8 bpp ok 16 bpp ok 32 bpp ok
1280x960 8 bpp ok 16 bpp ok 32 bpp ok
1280x1024 8 bpp ok 16 bpp ok 32 bpp ok
1360x768 8 bpp ok 16 bpp ok 32 bpp ok
1366x768 8 bpp ok 16 bpp ok 32 bpp ok
1440x900 8 bpp ok 16 bpp ok 32 bpp ok
1600x900 8 bpp ok 16 bpp ok 32 bpp ok
1600x1024 8 bpp ok 16 bpp ok 32 bpp ok
1680x1050 8 bpp ok 16 bpp ok 32 bpp ok
1768x992 8 bpp ok 16 bpp ok 32 bpp ok
1920x1080 8 bpp ok 16 bpp ok 32 bpp ok
Creating AudioMixer...
Audio opened using format: 22050 Hz 2 Channels
Timbers Precached: On play only
OGG Vorbis Digital Music: Disabled
Trying: `FMOpl'
Success!
Midi Output: Enabled
Starting a BLACK GATE game
Game path settings:
Static : D:\Programs\Origin Systems\Ultima7\static
Gamedat : C:\Users\Grant\AppData\Local\Exult\blackgate\gamedat
Savegame: C:\Users\Grant\AppData\Local\Exult\blackgate
Patch : D:\Programs\Origin Systems\Ultima7\patch

Timbers Precached: On play only
OGG Vorbis Digital Music: Enabled
Trying config specified Midi driver: `MT32Emu'
Failed!
Trying: `FMOpl'
Success!
Midi Output: Enabled
Opening digital SFX's file: "/sqsfxbg.flx"
Destroying AudioMixer...
Destroying MidiDriver...

Stderr
Warning, trailing slash in path: "\"
Warning, trailing slash in path: "\"
SDL Reports 640x400 16 bpp and 32 bpp windowed surfaces are not OK. Windowed scalers may not work properly.
SDL Reports 640x400 16 bpp and 32 bpp windowed surfaces are not OK. Attempting to use 16 bpp. anyway
SDL Reports 960x720 16 bpp and 32 bpp windowed surfaces are not OK. Attempting to use 16 bpp. anyway
Coldn't create inter surface: Unknown pixel format
Coldn't create inter surface: Unknown pixel format
Failed to initialize midi player (code: 1)


I do not know why that many map numbers are showing up. I do not have any files or directories named map01, 02, etc. in either static or patch directories. There is a map01 directory in the keyring mod folder but I'm not even running that when the error comes up with Exult Studio.

did you start Exult Studio from Exult by entering map edit mode? Does saving and reloading work in Exult?
Are there map folders in Gamedat : C:\Users\Grant\AppData\Local\Exult\blackgate\gamedat ?

is there anything in D:\Programs\Origin Systems\Ultima7\patch ?

I'm fishing as it is an odd bug.

The crash occurs whether I start it in game or if I start it on while not running a game.

Saving and loading appear to work properly.
There are no subfolders in the blackgate\gamedat folder.

The folder contents are
exult.ver
flaginit
frames.flg
gamewin.dat
identity
monsnpcs.dat
newgame.ver
notebook.xml
npc.dat
saveinfo.dat
schedule.dat
scrnshot.shp
u7ireg00 - u7ireg8f
usecode.dat
usecode.var

Damn... I can reproduce it on my Windows 10 VM. Also version 1809, build 17763.134

My guess is: we are using very old dlls for the GTK stuff to keep compatibility with old Windows versions. While we have decided to leave them behind it seems the Exult Studio download is still having those.
And I suspect these have some kind of incompatibility with Windows 10's fall upgrade.

What are the steps to reproduce? Bug number?

Newest bug in the tracker
But the steps are: Windows 10 version 1809, install Exult Studio, start it, click on a menu item.
That's all it takes.
https://sourceforge.net/p/exult/bugs/2034/

It seems it is the latest Windows Update that causes the issue.

And yes, using the Exult git branch that uses newer dlls etc for Windows has no problem for Exult Studio.

How do the mortals that walk among the code gods acquire such installers?

We have to convince Marzo to merge the branch and Kirben to make snapshots using this
When in dire need, I can provide the binaries without an installer and possible crashes

If you've got potentially usable binaries, I'll give them a try.

Yeah, I'd say, upload them. More will likely run into the same problem?

I've been holding off a Windows update for weeks now (I get the feeling it's 1809, MS parked 22 gb on my disk), so I'll be grateful with those files when the update is inevitably forced upon my poor computer.

I've got to go back to make a better build. This ones was just to tst stuff out for Marzo...

I would benefit from it as well. As part of writing some "smite" code I want to check the valid dead body shapes.

ok, here it goes. BUT be aware this is from an experimental branch of the Exult code which should be more stable but might introduce other problems. Let us know if you have any.
Best put it all in a new folder and don't install Exult or Exult Studio over the versions from this zip.
And I only quickly tested it on Windows 10 64bit, all other OS might break.

https://www.dropbox.com/s/896nl3bqdgse2 ... o.zip?dl=0

Thanks!

Well, Windows finally forced that update on me (restarting my PC while I had unsaved work nonetheless).
I don't have any crashes, but Ctrl+Alt+M doesn't bring Exult Studio up as it used to, not even with Dominus' files.

I'm not so handy with all this stuff though, so I'll just wait and hope for a new version.

That's odd - does it go into map edit mode (red grid)? If not try the other ctrl and alt keys

Nope, no map editing mode. When I alt-tab (after pressing ctrl+alt+m) there's no Exult Studio floating around either.
Other ctrl and alt key do not work either.

When I start Exult Studio separately and click connect, it doesn't go anywhere either.

studio_err.txt says "Failed to connect." along with a bunch of
Warning, trailing slash in path: "E:\Ultima VII\ULTIMA7\static\map01\"
and more lines like that.
Not sure if that's normal, never checked, but the folders mentioned don't exist, so I figure that's something from your Ultima installation.

Those irrelevant trailing slash warnings have been there for ages.

Hopefully the new builds will be out soon.

Seems as if Windows is intercepting the ctrl-alt-m key combination (or did you change the default keys for Exult?).
If you can't enter Map edit mode you cannot connect Exult to Exult Studio.

Do the other ctrl-alt cheat work?

Yeap, the cheats work. And no, I didn't change any keys.
Weird, huh? I wish I had a crash, then at least I'd have something.

Opening Exult Studio from Exult works for me with the experimental build. However only when playing in windowed mode. Sounds also do not appear to be working in the experimental build.

Exult + Exult Studio is meant to be used in Windowed mode, but if you switch to Windowed, bring Studio up from there and then go back to fullscreen, all works, I guess
As for the sfx, did you put the sfx files in the data folder of the experimental build?

@Gotcha, can you change the keybinding to something else to see what's happening? http://exult.info/docs.php#exult_keys
And does the old build launch it?

Now that stupefies me. I Changed the keys to Ctrl+M and it works! Both in the old version and your version.
I changed Create Gold (Ctrl+M) to Ctrl+Alt+M, and it doesn't work.

It's like the combination Ctrl+Alt+M is completely ignored.
All the other 3-key shortcuts work.

Ok, so far so good. Thanks for checking. Look into any other program that runs and might have hijacked this keycombo.
On my very pristine Windows 10, it's working fine.

Read through https://superuser.com/questions/999106/ ... g-a-hotkey
Especially the hint at the end with Process Explorer looks promising

And https://defkey.com/what-means/ctrl-alt-m might be relevant

Wow. Brain fart. I read your post, clicked the first link, but while I did, suddenly all the pieces fit together. I'm a dumb-dumb and here's what happened:

A few weeks ago I had problems making screenshots in a certain game I'm modding, so I installed Geforce Experience to help me with that.
It provides an in-game overlay and functions, like creating screenshots, videos, etc.
There are a bunch of shortcuts in this game overlay, and one of them, you guessed it, is Ctrl+Alt+M.

I completely forgot about installing this tool, and due to this thread and me receiving MS' latest update, I fully put the blame onto Windows. (I don't blame myself too much for that, because every major non-security update MS throws out breaks at least something. *grumble*)

I cleared all the shortcuts that I don't need, so that's a problem solved.

Thanks for your help! Knowing myself, I would not have thought of this in a long time. >_>

That was my first idea

No new official builds? May the Time Lord save us.

AFAICT it is now working in the latest snapshot. I have no idea if that is caused by the snapshot or whether MS fixed something on their end. Curios

The new snapshot works properly for me.
I think the problem was originally caused and then fixed by Microsoft as a fresh installation that was then fully patched did not have the bug.

Thanks for the confirmation!