*Official SEOW


Official SEOW Software Forum            

Bug Reports: SEDB73, MP4 v7.3.x, SEDCS v7.3.x

For bug reports and fixes, installation issues, and new ideas for technical features.

Moderator: SEOW Developers

Bug Reports: SEDB73, MP4 v7.3.x, SEDCS v7.3.x

Postby IV/JG7_4Shades » Thu Apr 20, 2017 4:59 am

This is the thread for bug reports for SEOW v7.3.
IV/JG7_4Shades
SEOW Developer

Image
IV/JG7_4Shades
 
Posts: 2141
Joined: Mon Jan 08, 2007 11:10 pm
Location: Perth, Western Australia

Re: Bug Reports: SEDB73, MP4 v7.3.x, SEDCS v7.3.x

Postby IV/JG7_4Shades » Thu May 04, 2017 10:12 pm

DCS and MP upgrade: v7.3.1
*) Fixed minor bug in the Iron Front support, for the Undo Analyze operation in the DCS
*) Improved verbose names display for admin user in MP
*) Added new ground movement mode: Simple+Bridges. This clamps units to cross rivers only at road bridges, elsewhere simple movement applies. Note that this re-numbers the CGM values, so check your settings in an in-progress campaign if you use v7.3.1 (Thor)

Now available for download. Enjoy!
IV/JG7_4Shades
SEOW Developer

Image
IV/JG7_4Shades
 
Posts: 2141
Joined: Mon Jan 08, 2007 11:10 pm
Location: Perth, Western Australia

Re: Bug Reports: SEDB73, MP4 v7.3.x, SEDCS v7.3.x

Postby IV/JG7_4Shades » Sat May 06, 2017 9:27 am

And another bug fix, this time only for the DCS.

*) Corrected bad string init for Simple+Bridge mode
*) Updated Factory Default settings for new CGM model
*) Corrected trigger logic for case where the defined signaller is an active barraging unit (Gross)

Note that it is not recommended to use active barraging units, i.e. "AIF" units that have valid barrage orders (indirect fire orders) as signallers. AIF units that are in direct fire mode can be used as signallers with no problem.

Cheers,
4S
IV/JG7_4Shades
SEOW Developer

Image
IV/JG7_4Shades
 
Posts: 2141
Joined: Mon Jan 08, 2007 11:10 pm
Location: Perth, Western Australia

Re: Bug Reports: SEDB73, MP4 v7.3.x, SEDCS v7.3.x

Postby IV/JG7_4Shades » Wed May 24, 2017 10:14 am

Gross suggested that we add a list of statistics archives to the MP-Statistics page, so old statistics pages from previous campaigns can be discoverable. Good idea!

Stats v7.3.2
IV/JG7_4Shades
SEOW Developer

Image
IV/JG7_4Shades
 
Posts: 2141
Joined: Mon Jan 08, 2007 11:10 pm
Location: Perth, Western Australia

Re: Bug Reports: SEDB73, MP4 v7.3.x, SEDCS v7.3.x

Postby PA-Dore » Wed May 24, 2017 12:31 pm

Good idea yes, in the pass I kept them in an old folder^^
User avatar
PA-Dore
 
Posts: 462
Joined: Thu Nov 01, 2007 8:58 am
Location: Savoie-France

Re: Bug Reports: SEDB73, MP4 v7.3.x, SEDCS v7.3.x

Postby IV/JG7_4Shades » Thu May 25, 2017 8:51 pm

Added extra details to Statistics Archives listings; Statistics v7.3.3

Pilot Count
- calculated from the number of *.jpg files inside the archive folder

Mission Count
- calculated from the number of SE-*.html files inside the archive folder
IV/JG7_4Shades
SEOW Developer

Image
IV/JG7_4Shades
 
Posts: 2141
Joined: Mon Jan 08, 2007 11:10 pm
Location: Perth, Western Australia

Re: Bug Reports: SEDB73, MP4 v7.3.x, SEDCS v7.3.x

Postby 22GCT_Gross » Fri May 26, 2017 6:41 am

Thank you much Shades. That gives a much appreciated summary of the seow activities across the years
22GCT_Gross
 
Posts: 299
Joined: Fri Apr 13, 2007 1:13 pm
Location: Italy

Re: Bug Reports: SEDB73, MP4 v7.3.x, SEDCS v7.3.x

Postby IV/JG7_4Shades » Sun Jun 04, 2017 11:31 pm

New patch update: DCS v7.3.3, MP v7.3.5, Statistics v7.3.4

*) Corrected iterator/break for meta forces loader in DCS
*) Added support for captured/surrendered forces in Statistics
*) Added capture/surrender support to meta-SEOW/Iron Front scripts
*) Added foggy breath support for cold weather in Iron Front missions

Enjoy!
IV/JG7_4Shades
SEOW Developer

Image
IV/JG7_4Shades
 
Posts: 2141
Joined: Mon Jan 08, 2007 11:10 pm
Location: Perth, Western Australia

Re: Bug Reports: SEDB73, MP4 v7.3.x, SEDCS v7.3.x

Postby 22GCT_Gross » Mon Jun 12, 2017 1:34 pm

Mike,
the MP-News.php now includes the Provence Sector, but no Provence database is available and other php files are not including that as well.
So, a mere update returns an error in the Mission Planner to me.
At the moment I have commented the MP-news.php line 475 and that solved the issue.
Code: Select all
//$headlines .= SectorLinkNews("Provence");
22GCT_Gross
 
Posts: 299
Joined: Fri Apr 13, 2007 1:13 pm
Location: Italy

Re: Bug Reports: SEDB73, MP4 v7.3.x, SEDCS v7.3.x

Postby IV/JG7_4Shades » Wed Jun 14, 2017 9:47 pm

Thanks Gross, my mistake. I will issue a complete patch to include full support for Provence.
IV/JG7_4Shades
SEOW Developer

Image
IV/JG7_4Shades
 
Posts: 2141
Joined: Mon Jan 08, 2007 11:10 pm
Location: Perth, Western Australia

Re: Bug Reports: SEDB73, MP4 v7.3.x, SEDCS v7.3.x

Postby IV/JG7_4Shades » Mon Jul 24, 2017 5:19 am

I have just released a small update to the DCS, v7.3.4 and a related update to the meta-SEOW code in MP4public.

File Upload Feature (new)
The DCS now has a revised "Remote Functions" tab, with a new "File Upload" section appearing. This feature allows you to specify a file (in your local PC filesystem) that can be uploaded to a particular FTP server of your choice. The upload takes place at the beginning of each Analyze stage. I added this feature to support SEOW campaigning in the situation where multiple people may be using a single remote SEOW server, e.g. it may be useful to upload logfiles automatically. In the following I describe how the feature works.

The File Upload section contains two fields to be filled out by the DCS user. If either field is not filled out, the feature is ignored.

The Local File field is where you specify what file on your PC you wish to have copied to the remote FTP server each Analyze stage. Any file is ok, but the larger the file the longer the transfer time. If this field empty or is showing "undefined", or has a pale blue background then the feature is inactive.

The FTP Server URL field is where you specify the FTP address, credentials and destination path for your local file transfer. If this field has a pale blue background then no valid URL has been entered. A valid URL has the general format:

Code: Select all
ftp://username:password@serveraddress:port/folderpath/filename

where
username is the ftp login name (avoid special characters, use HTML encoding for @ "%40" if needed)
password is the ftp login password
serveraddress is the domain name or IP number of the FTP server
port is the port number of the FTP server
folderpath is the destination folder name for the local file once transferred
filename is the name that the local file will be given once transferred

As an example, consider an FTP server "my.ftpserver.com" listening on port 21 for connections from user "fyodor" with password "Brno". You decide you want to upload "C:\Program Files (x86)\Ubisoft\HSFX\eventlog.lst" to the remote folder "HSFXlog" in fyodor's account and call it "latest_eventlog.lst". In this hypothetical example you would set:

Code: Select all
Local File = C:\Program Files (x86)\Ubisoft\HSFX\eventlog.lst
FTP Server URL = ftp://fyodor:Brno@my.ftpserver.com:21/HSFXlog/latest_eventlog.lst


Setting these two fields correctly (with acceptable contents) will result in the field backgrounds going white.

Of course, even if you define the File Upload field values correctly, the FTP upload will only work properly if your named FTP server already has the appropriate account established and operating. It is the user's responsibility to ensure this. In testing this feature works reliably and well for properly configured settings. When the DCS Analyze button is pressed the FTP transfer is commenced immediately and the DCS progress bar will display yellow as the file is transferred. Once the transfer is complete the progress bar will revert to green and the usual Analyze process will continue.

To accompany this feature I have modified the meta-SEOW log analyzer in the MP to scan a log folder for the latest logfiles (*.RPT, *.txt) and proceed with the latest logs for all defined meta-maps. This means that the campaign admin can build a SEOW mission remotely (DCS Build) which produces a single HSFX mission and multiple Iron Front missions. Different people can download different Iron Front missions in zip format, host them and upload their logfiles to the remote SEOW ftp server folder. Once all the Iron Front log files are assembled, the campaign admin can remotely perform a single DCS Analyze to advance the campaign state.

I am sure that other people will find their own creative uses for the File Upload feature.

Cheers,
4Shades
IV/JG7_4Shades
SEOW Developer

Image
IV/JG7_4Shades
 
Posts: 2141
Joined: Mon Jan 08, 2007 11:10 pm
Location: Perth, Western Australia


Return to Technical Discussion

cron