F2LC problem

jargo said:
If you could test it a little before i post it on site that would be great.
Click to expand...

Well, it seems I picked the right time to switch over to FSE :o This 1.5a version is really good! Including the compiler and precompiler files with FSE makes it much easier for people to use. Now you need nothing else, just FSE, very nice. It allowed me to point to my custom named fallout2.cfg (fo2xp.cfg), and knew from there where to find my game files in the source tree. If I change the cfg file to point to the game (dist) tree, FSE goes there instead (perfect). And the new post-compile batch file execution allowed me to add a copy of the compiled file to both my source and dist trees. Excellent! And I like how you have the procedure names along the right side of the screen for easy navigation within the script.

So far it looks perfect, the only problematic thing is that it doesn't seem to do the "open file from dat". If I select that and point to a DAT file it always says "no file opened". This doesn't bother me because I always have a complete set of FO1 and FO2 extracted on my hard drive.

Very nice work Jargo, and thanks for adding those new features.
I'm using 1.5a every day now, and I'll let you know if I find any bugs.
 
So far it looks perfect, the only problematic thing is that it doesn't seem to do the "open file from dat". If I select that and point to a DAT file it always says "no file opened". This doesn't bother me because I always have a complete set of FO1 and FO2 extracted on my hard drive.
Click to expand...

As i understand when you open Undat then it does not open master.dat or other file showing no file opened error.
This error is show when undat can't find Dat file.
Normally Undat on start opens master.dat.
It takes master.dat location from cfg file (master_dat) and search for patch000.dat in same location.

I found a bug in opening patch000.dat file(it was searching in wrong dir) but master.dat and any chosen *.dat should be loaded ok.

Very nice work Jargo, and thanks for adding those new features.
I'm using 1.5a every day now, and I'll let you know if I find any bugs.
Click to expand...

Glad you liked, if you need something in next version just say.
 
jargo said:
As i understand when you open Undat then it does not open master.dat or other file showing no file opened error. This error is show when undat can't find Dat file. Normally Undat on start opens master.dat. It takes master.dat location from cfg file (master_dat) and search for patch000.dat in same location.

I found a bug in opening patch000.dat file(it was searching in wrong dir) but master.dat and any chosen *.dat should be loaded ok.
Click to expand...

Okay, if I change the FSE settings to use the Fallout2.cfg file in the \Fallout2 directory then, if I select file open from dat, and click on master.dat, I get the error no file opened. If I click on *.dat instead and point to master.dat, it does allow opening files from master.dat. I can also open patch000.dat this way.

However, if I change the FSE setting to use my custom fo2xp.cfg, it will not open any dat files, although everything else in FSE seems to work properly with that config file. The FO2LC loader I use was set up to look for a custom cfg file instead of fallout2.cfg.

A couple of more things I noticed. When I specify the config file in FSE settings, it has the default file name fallout2.cfg and the file type says "Fallout2 config file (Fallout2.cfg)". Shouldn't that type be *.cfg? My custom file doesn't appear in the file chooser since it is not named fallout2.cfg, but if I type over the fallout2.cfg name it lets me change the file to my custom config name (fo2xp.cfg). and then everything works in FSE (except for the dat file opening).

The menu in FSE has the "Edit" function inaccessible unless I have a script source file open. This means I cannot select the "Options" from the menu, to configure FSE, unless I open a script source file first. The icon for settings is there and works, but the menu option for settings is inaccessible.
 
jargo said:
I think i nailed that bug. The problem was that FSE reads *.cfg only on start, so when you change config file in settings new cfg is not read until program is closed and opened again.
Click to expand...

Okay with new version, the selection of custom cfg file works fine now, My custom file shows up in file selector and I don't need to type over the default name. The options in the edit menu are now accessible without a script file open.

Still some problem with open from dat file. With this last version, I can open master.dat in \fallout2 directory, but it won't let me open it if it's in another location. The way I have my mod arranged is a new directory outside of fallout: C:\FO2XP and in that directory are copies of master.dat, critter.dat, the \sound\music files, and my mod files. I like it this way because its completely separate from fallout, and doesn't require anyone changing their fallout installation.

So with the files arranged as above, I can open the master.dat from \fallout2, but it won't let me open the master.dat from \fo2xp. It gives the message "No File Found C:\FO2XP\MASTER.DAT" even though the file is there, and file permissions are okay (I checked).

I have another copy of master.dat in a directory \fallout2-source\dat, and I can't open that either. In both of these cases I am clicking on the *.dat button in FSE and browsing to the master.dat file.

It appears that there is still some dependency on \fallout2 directory, even if I browse to the dat file I want to open. Either that or FSE is not finding that dat files properly.


EDIT: I forgot to mention a typo in settings screen:
Close compile window after bath file
 
I have another copy of master.dat in a directory \fallout2-source\dat, and I can't open that either. In both of these cases I am clicking on the *.dat button in FSE and browsing to the master.dat file.
Click to expand...
That's weird, the *.dat button have never had any dependencies on Fallout2 folder it is used to open any dat file.
I can open any dat at any folder using it.

It works like this:
It calls 'open dialog' and then directly OpenDaT function.
The error message is from start of OpenDAT and looks like that:
Code: 
if not fileexists(FileName) then
    begin
        application.MessageBox(pchar(Here is the error message that you see));
        if speedmaster.Down <> true then // This to try open master.dat if last opened file was not master.dat
        begin
            speedmaster.Down := true;
            speedmaster.OnClick(self);
        end;
    exit;
    end;

So as you see the error is caused by if not fileexists(FileName) then line.
Fileexists function work well on NT.
If you have NTFS file system then maybe privileges for c:\FO2XP\ folder or file are set wrong and FSE cannot have access to this files(and it can open Fallout2 folder).
 
Jargo ... okay this was a false alarm ... or a bugged bug report hehe .... I'm not sure what was wrong with the master.dat I had in my custom folder, the permissions seemed okay, but I replaced it with a copy of the master.dat from \fallout2 and now the file open from dat works. Sorry about that.

All looks well with FSE now :)
 
OK and don't worry i would not found this bug about patch000 without that. ;)

Ah and a minute ago found another one when showing Msg file references.

If you find something new just give a sign.
 
You must log in or register to reply here.
Back
Top