@Lee
@Preben

Thanks in advance for your time
Since you guys be working on bugs - maybe you can investigate an issue I found the other day when testing a standalone build.

First the build works fine, in that everything is copied over, and runs as expected.
Secondly most of the media is custom.

The Issue:
So in my game, the second level it is open world, and the following third level is in a space type setting where terrain and water are turned off.

When flying a spacecraft around the level ( thanks AmenMoses) there are models from the previous level appearing on the map like so:

None of the models in this screenie are actually on the current map (level 3), but are only used in the previous one (level 2).

So creating a standalone build using allowfragmentation=2 fixes the rogue models issue, but:
- takes a while to display the loading screen between levels,
- and final screen feels kinda clunky
- - - like takes a while to show the final screen, and when you click continue it takes a while to load main menu
The resulting experience tends to make you feel the game has locked up.

It would help if the engine just loaded the loading screens immediately and just did it's thing behind the curtain so-to-speak.

Anyway, just wondering if you guys can take a look see
I know other devs are having issues with standalone, so they may chime in as well.

Thanks for reading.

OldFlak....

absolutely

The issue above happened to me a long time ago and I cant remember what I did to fix it unfortunately...

What I can do is to report standalone issues I am experiencing:

- Missing entities

- strange increase in movement speed of the player

- crashes during loading screen

- allowfragmentation = 2 does help with crashes but deleted weapons wich is bad when you have a shooter game

- draw call optimizer debug mode cant be entered? It was f11 twice and then pressing 9 ? But all I see is "shadows" highlighted and no change in the draw call meter.

bevore pressing 9


after pressing 9




---------------------------------------------------

Other than that, gameguru actually has improved a lot in terms of standalone export.
I have some huge EBE buildings in my levels wich are carried over properly now.
All in all this is a good performance but still could be way better. If someone has a game on steam, they wanna make sure that the engine related problems are as few as possible.

Thanks for taking the time to read!
- Duchenkuke

Perhaps setting GG to clear memory between levels would fix it? As a temporary fix. It will take longer to load, but may fix this issue. I think it is the memory fragmentation setting, but not used GG in quite a while now.

In those screenshots you have not pressed F11 twice, if you had you would not have the hardware info and list of disablement below.

Checking hte instructions you don't need to press it twice anyway, just once then press 9. (don't prfess and hold 9, just press it once, then go to tabtab to see the drawcalls)

@belidos, thanks for the heads up, it was told me wrong then. I asked on a discord server and got this information there

Yes, please.
Recurring issues. And yet the UI test maps are so reliable. Why not Standalone?
I hope my current project isn't destroyed by the broken GG Standalone system...

Any documentary on the whole of Stand alone issues?

What messed up on it exactly ?

Yes. Thanks for asking Synchromesh. Well, I haven't officially built a map for many
months. I've been studying lua instead, waiting for upgrades to the compiling
of the stand alone. Of course very soon I will be trying to put it all together
and after the digital work, I don't want to be hampered by a decrepit compiling
system.

I think I saw someone post some tips once on how to work through certain stand
alone issues... so I wanted to look it over, but couldn't find that thread again.
Will search further. Thanks again.

The issues with standalone I find do not actually seem to be the engine but more the assets.
Stock and your own may work really well but its entirely possible that when it comes to old classic assets or non updated 3rd party assets from the store there could well be issues of missing textures etc … You can bet the engine has in fact put the model there as its supposed to but just cannot read the paths to find the textures ..

Mine are 100 % custom so I know if they work in one level they will work in others so a standalone every session after I work on my game may seem like overkill but there are also scripts to consider and check in that test. nevertheless I do them.

From all the reports I have read standalone is fine as long as the assets are made in the correct and up to date format. If not then that's where the problems start to show up. A standalone build can take all of 3 minutes compared to the 24 / 48 hours in Radiant back in the day so my advice is do one after every heavy session at least just to make sure they are all transferring correctly and all is well.

Hey synch i think you actually helped save one of my standalone issues. You mentioned texture path and so i decided to go see what happened with my assets (which are old from GG fantasy DLC, but originally from FPSC). While the characters did show up in a preview standalone, they dont now, for whatever reason. Anywho since i went and checked if textures carried over this in fact wasn't the case, and so i found the problem!

I think Ive also identified the exact issue. These models on the DLC's on steam are referencing TGA paths and not DDS. GG the engine normally converts them, but it appears the standalone sometimes does not. For example:

textured = Desiccated Priest_noweap_D2.tga

Will post on github. Instead of making the standalone engine try to figure out this issue, I think the DLC packs should be updated to use the paths of .DDS instead of TGA and leaving it to the engine to change or search out DDS.