Author Topic: RELEASE: Deneb III  (Read 16445 times)

0 Members and 1 Guest are viewing this topic.

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
I was afraid of that.  Try extracting these into the same directory.
http://scp.indiegames.us/builds/temp/FastDebugDLLs.7z

 

Offline Colt

  • 27
  • Needs more dakka
    • Steam
That worked. Upon pressing "ready" I got this brief error.

Code: [Select]
Warning: DenebIII-3.fs2(line 205):
Warning: Variable 0 has the same name as an eternal variable. One of these should be renamed to avoid confusion
File: parselo.cpp
Line: 301

Mission's loaded, gonna play and edit this post if I come across anything else.

EDIT: My bad. Yeah selected wrong version.

EDIT 2: Well, this is strange. In FSO settings I have the fs2_open_3_8_1_AVX2-FASTDBG selected, but pressing "play" will briefly say "fso launching" and then nothing happens. Going options>fast debug will start the game however, but in the 19.0.0 RC build (I changed preferred engine stability to nightlies, and in that case it used the most recent nightly build).
« Last Edit: October 11, 2019, 05:03:34 pm by Colt »

 

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
That still says Variable 0, instead of the variable name.  Are you sure you are running the build I provided?

 

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
@Colt, ngld had this to say:
Quote
Yeah, those were the right steps. The issue with "FSO is launching..." only appearing for a short moment either means that FSO crashes very early or some other weird issue prevented Knossos from starting FSO.

In order to continue making debugging this, can you switch to a non-Knossos installation?  Deneb III is on the FSO Installer, so you should be able to install that and then use the build I provided without having to go through Knossos.

You may need to launch the debug build via wxLauncher once to select the Deneb III mod and configure your settings.  After that, you can launch the build directly.

 

Offline Colt

  • 27
  • Needs more dakka
    • Steam
Hmm. I can not find Deneb III, which is strange because I remember seeing it when I was still using FSO/wxlauncher last year (current FSO Installer is V2.3.2 right?)

I'll copy/paste the mod from my knossos folder into the one wxlauncher uses. Already downloaded the 19.0.0RC AVX update. Changing the .jsom to mod.ini worked last time I fiddled around with them.

 

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
Looks like the SectorGame host is blocking automatic downloads again; that's why Deneb III isn't showing up.  I'll ping Hunter and ask what's going on.  You can download it manually from here if you want.  Copy/pasting the mod from Knossos might work but I've never tried it.

Alternatively, a new nightly build that includes the fixes is in progress.  It's currently waiting on the integration tests, which have been blocking for the last few hours, but as soon as that's posted you will be able to select it in Knossos.

 

Offline Colt

  • 27
  • Needs more dakka
    • Steam
 Just replayed the campaign with the new nightly and everything worked out! That was a very fun mini-campaign from beginning to end. :yes:
Spoiler:
That final battle was pretty neat, but I don't know how I feel about the Legion going down. On the one hand, it's an absolute tragedy; ten thousand of GTI's best instantly vaporized or sucked out into space, with deadly consequences because of it after the war (ahem-Silent Threat-ahem). On the other hand, watching it get hulled and turned into a derelict instead of just outright exploding was an amazing sequence.

 

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
Wonderful!  Glad you enjoyed it! :D

Yes, I worked hard on that sequence.  Scripting really came in handy for the explosions and particles. :)


To tie up loose ends now that a new FastDBG build is available, can you try loading mission 3 again and see if the "Variable 0 has the same name as an eternal variable" message is different?

 

Offline Colt

  • 27
  • Needs more dakka
    • Steam
Everything seems fine with the debug too. No crashing or windows popping up when Omega launches. I tried uploading a debug log just to make sure everything was 200% fine but after almost 10 minutes of waiting I closed the link.

 

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
Er, wait.  If you played mission 3 through the Tech Room, that error would not appear.  It is only checked during campaign mode.  Would you mind playing through (or cheating through) missions 1 and 2 again, then loading mission 3 in the debug build? :nervous:

 

Offline Colt

  • 27
  • Needs more dakka
    • Steam
Aight, just did a full run on debug. I've included all other errors I received, but they're all minor model-related bugs (they're in "hidden" to keep this post tidy  :p).

Hidden Text: Show
Upon starting the campaign:
Code: [Select]
Warning: Not all subsystems in model "capital01-multidock.pof" have a record in ships.tbl.
This can cause game to crash.

List of subsystems not found from table is in log file.

File: modelread.cpp
Line: 805


Warning: Couldn't open glowpoint texture 'glow_white'
referenced by model 'GVT_Qeb.pof'

File: modelread.cpp
Line: 1979

Mission 1, when Omega and Lambda wings arrive:
Code: [Select]
Warning: Unable to find 'turret04' in ship subsys_list!
File: missionparse.cpp
Line: 2349

Warning: Unable to find 'turret03' in ship subsys_list!
File: missionparse.cpp
Line: 2349

Warning: Unable to find 'turret02' in ship subsys_list!
File: missionparse.cpp
Line: 2349

Warning: Unable to find 'turret01' in ship subsys_list!
File: missionparse.cpp
Line: 2349
Nothing on mission 2.

Mission 3 when it loads:
Code: [Select]
Warning: DenebIII-3.fs2(line 205):
Warning: Variable saveexist has the same name as an eternal variable. One of these should be renamed to avoid confusion
File: parselo.cpp
Line: 301

EDIT: This run was done with the 20191015 nightly version.

« Last Edit: October 16, 2019, 08:15:32 pm by Colt »

 

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
Excellent, thank you!

These are minor errors, and most of them can be fixed easily, but that variable message is intriguing.

The shipsave script requires the use of the saveexist variable.  Many campaigns use this script, including Deneb III, but there are no eternal or persistent variables in the Deneb III campaign with the name "saveexist".  My guess is that one of the campaigns you previously played marked this variable as persistent, and this caused an "infection" where it complains about any other campaign that uses this variable.

I will have to ask karajorma to comment on this.

  

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
It sounds like the eternal variable warning is just a nuisance left over from someone else's campaign.  As for the rest of the errors, I've fixed them and uploaded a new version of Deneb III to the FSO Installer, to Knossos, and to the Phoenix grand prize area. ;)