Author Topic: RELEASE: Sol: A History Upgraded  (Read 90628 times)

0 Members and 1 Guest are viewing this topic.

Re: RELEASE: Sol: A History Upgraded
[launcher]
modname      = Sol: A History;
image255x112 = SAH.bmp;
infotext     = Sol: A History- upgraded;

[multimod]
secondrylist = FreeSpacePortMVP,FreeSpacePort,MediaVP;

 

Offline CT27

  • 211
Re: RELEASE: Sol: A History Upgraded
Are you using a nightly?  #Ignored Mission File Names isn't in 3.8.0.

I was using a post 3.8.1 nightly.  I take it I should just use the regular 3.8.0?


As for Nightmare's post:
Do I then need to add "_2014" or "_38" to the end of those? 
I've had to do that in the past to get certain VP versions to be used.

 
Re: RELEASE: Sol: A History Upgraded
I tested this with the 2018 MVPs.

As for builts, I'm always using the most recent ones from the nightly board. Easiest way to avoid compatibility issues (this doesn't apply to MVPs, however).

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: RELEASE: Sol: A History Upgraded
secondrylist
I think we can guarantee you're not using a launcher old enough to need that ancient typo.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 
Re: RELEASE: Sol: A History Upgraded
5.5gold for retro!

 

Offline CT27

  • 211
Re: RELEASE: Sol: A History Upgraded
Are you using a nightly?  #Ignored Mission File Names isn't in 3.8.0.

I used FSO 3.8.0 (official, not a nightly) and got the same error message.

Error: sah-mod.tbm(line 16):
Error: Missing required token: [#END]. Found [#Ignored Mission File Names] instead.

File: parselo.cpp
Line: 290



 
 

Offline ngld

  • Administrator
  • 29
  • Knossos dev
Re: RELEASE: Sol: A History Upgraded
3.8.2 hasn't been released, yet.

@CT27 The nightly you used last time was probably too old. Try using a more recent nightly. Also, please mention which nightly you used next time this comes up.

I used FSO 3.8.0 (official, not a nightly) and got the same error message.
Since 3.8.0 is even older than the nightly you used before, this is not suprising.

Are you using a nightly?  #Ignored Mission File Names isn't in 3.8.0.

I was using a post 3.8.1 nightly.  I take it I should just use the regular 3.8.0?
That was a misunderstanding. PIe thought you were using 3.8.0 and was trying to tell you that you need a nightly.

 

Offline CT27

  • 211
Re: RELEASE: Sol: A History Upgraded
I just tried the January 9, 2019 nightly.


I saw the MediaVPs 3.8 screen but then a "warning" box came up.  However, this box had no text in it.  I clicked on the button that one would usually click on to pass the screen.  When I clicked on the button to try and start the campaign, there was a command briefing picture present but no text.  The regular mission briefing had no text and only ship icons present (the ship icons were just on a black background without the usual grid lines that are on a mission briefing screen).  When I tried to start a mission, it crashed.


For some reason campaigns don't seem to show stuff properly whenever I use a nightly beyond October 31, 2017.
Also, for what it's worth, my computer's graphics right now are AMD Radeon HD 6770.
« Last Edit: February 12, 2019, 09:06:16 pm by CT27 »

 

Offline Trivial Psychic

  • 212
  • Snoop Junkie
Re: RELEASE: Sol: A History Upgraded
I used to experience lighting issues when consistently using any builds newer than the 2017-10-31 build.  I say consistently, because often I could use a newer build but only for a while (time indeterminate) before it would break.  After that point, that build would not longer work.  All that changed when I performed a system rebuild and got a new video card.  After that point, the graphical anomalies disappeared.
The Trivial Psychic Strikes Again!

 

Offline CT27

  • 211
Re: RELEASE: Sol: A History Upgraded
I used to experience lighting issues when consistently using any builds newer than the 2017-10-31 build.  I say consistently, because often I could use a newer build but only for a while (time indeterminate) before it would break.  After that point, that build would not longer work.  All that changed when I performed a system rebuild and got a new video card.  After that point, the graphical anomalies disappeared.

What card were you using before and which one are you using now?

 

Offline Trivial Psychic

  • 212
  • Snoop Junkie
Re: RELEASE: Sol: A History Upgraded
Old = HD5770
New = RX570
The Trivial Psychic Strikes Again!

 

Offline CT27

  • 211
Re: RELEASE: Sol: A History Upgraded
Old = HD5770
New = RX570

For me I currently have a Radeon HD 6770 and my next computer that I get later this year will probably be a GTX 1070 (I know that's not the newest one but I saw a good deal on a prebuilt system with it and I've heard that should be more than enough for FSO).

 

Offline SL1

  • 26
Re: RELEASE: Sol: A History Upgraded
Any tips for increasing FPS? I'm dropping below 30 if I try to watch the whole battle in End of an Era, so I need to turn some stuff down. I'm not very knowledgeable about this kind of thing, though, so I don't really know what the biggest FPS killers are.

 
Re: RELEASE: Sol: A History Upgraded
Shadows are by far the biggest framerate killer, especially on AMD GPUs. If that's not helping try decreasing the lighting quality in the in-game settings to 4, which disables laser lighting, really helps with high firerate weapons and huge battles.
If that's still slow start disabling unnecessary HUD elements or setting them to popup. You don't really need a constant reminder that Auto-target is on and auto-speed is off for example, you can safely set those to popup. The vector graphics used for FSO's HUD aren't exactly well optimised so you can gain some frames there.
[19:31] <MatthTheGeek> you all high up on your mointain looking down at everyone who doesn't beam everything on insane blindfolded

 
Re: RELEASE: Sol: A History Upgraded
You can also disable "deferred lighting" in launcher graphic settings. If memory serves, it will disable the majority of lighting effects which should drastically increase FPS.
Mito [PL] - Today at 8:52 PM
I was supposed to make a short presentation about basics of optical fibers and here I am, listening to Eurobeat while reading about quantum cryptography.

 
Re: RELEASE: Sol: A History Upgraded
Thanks for the release! Really loving it so far.

The only issue I have now is in the second campaign. I just did the mission where you get the new fighter along with a new HUD. Problem is, that HUD is low resolution and really messes up my 2560x1440 graphics, as the low-res parts are misshaped and not aligned correctly. Anything I can do about this?

 

Offline Admiral Nelson

  • Resurrecter of Campaigns
  • Moderator
  • 211
  • The GTA expects that every man will do his duty.
Re: RELEASE: Sol: A History Upgraded
Do you have a screenshot?  I developed this release on a 1440p monitor without such issues.
If a man consults whether he is to fight, when he has the power in his own hands, it is certain that his opinion is against fighting.

 
Re: RELEASE: Sol: A History Upgraded
Sure!

First screen (as reference) is from the very first mission. This is how it is supposed to look like.

Second screen shows the beginning of "Darkness Falls" from the second campaign (second mission with the new fighters, but the one before was the same). Looking at the images today I assume it is a problem of font size. Notice that in the target cam window some values overlap, as they don't fit its size. But you can also see that the comms text (window as well as upper left corner) is the correct, smaller size.

Third screen shows that the damage window suffers from the same issue. In the secondary weapons list, the timer for the Hellstorm is unreadable because of overlapping.

Any idea what I can try to solve this, or at least to identify the cause? It might not look that bad on the screenshots, but in motion I find it to be extremely irritating.

All screens were made with the same pilot profile. I have not changed anything in the game's HUD config. The only ingame options I changed at all were maxing out all graphics settings, before even beginning to play Sol:AH and not changing anything since.

Edit: After playing a few missions with the issue, I have to retract yesterday's statement of HUD elements being misshaped. The combination of new HUD and the font size issue apparently combined to that false impression. Still, the overly large font is still bugging me, not only because of the overlapping, but also because the HUD is now covering so much screenspace (especially with many wingmen and a large escorts list).

[attachment eaten by a Shivan]
« Last Edit: May 30, 2019, 07:29:17 am by Knecht Ruprecht »

 

Offline Admiral Nelson

  • Resurrecter of Campaigns
  • Moderator
  • 211
  • The GTA expects that every man will do his duty.
Re: RELEASE: Sol: A History Upgraded
Yeah -- that is the old BtRL HUD.  I've scrapped that from the next version of the mod, as the interface art is too small as you rightly point out.  The only fix really is to redo or replace it.  It did not bother me that much when I was playing it myself, but I can see how it would bother others.  One temporary option would be to create an empty text file called "EA-hdg.tbm" in your data/tables folder, which would leave all ships with the FS1 HUD.  Alternatively you can wait for the next version with the new Inferno ships and new HUD.

Here are a couple of videos showing the new WIP HUD.  Note that the artwork is larger and so not squashed.


If a man consults whether he is to fight, when he has the power in his own hands, it is certain that his opinion is against fighting.