Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Engine revisions

A topic by xxxLEOPARDxxx created Apr 19, 2021 Views: 608 Replies: 12
Viewing posts 1 to 10

Hey!

Version 193

There are jungle bugs, freezes or crashes. And also, there is no grass at all. I had to roll back for now.

After version 183+, such logs often began to appear in error files.



I have no answers.  I do not have these problems with any of my versions with any of the available mods: COAS, CT, CT Historical, ERAS, GOF 1.2, GOF 2.0, GOF 2.5, on my machines.

You can try adding  to start.ini:

cncLevel = 0

When there are a lot of high-poly models of ships in the sea, such bugs with rigging occur.




(1 edit)

By the way, I have a feeling that on my system the game is not using all cores / threads.

The teammate has a laptop, he has the same set of 55-60 FPS ships at sea. I have a PC and I feel a strong FPS drawdown, and the task manager shows that the CPU is loaded by 10%.

CPU type 12-Core AMD Ryzen Threadripper 2920X, 4300 MHz (43 x 100)

ASRock X399 Taichi Motherboard (1 PCI-E x1, 4 PCI-E x16, 3 M.2, 1 U.2, 8 DDR4 DIMM, Audio, Dual Gigabit LAN, WiFi)

System memory 130953 MB

Video adapter GeForce GTX 1080 (8 GB)


I just uploaded a version where the start.ini option will disable even more of the threading

cncLevel = 0

Try that to see if it helps.  I don't know why, but for some reason maybe your processor is crossing bounds that other processors don't.  I have tested both Intel and AMD processors that I have, and the thread blocking mechanisms appear to do the proper job to prevent threading problems, but since the only updates I have made in this area deal with threading, I made that cncLevel option disable some of the recent changes, so it will act like the old way.  Of course this will also revert it back to what the original game did for all this logic and make it single threaded in these areas, but that is how it was always done before anyway.

(1 edit)

I tried with this parameter. No, it didn't fix the situation.

Well, okay, not critical.


By the way, if I put the screenshotformat = png parameter in start.ini, then all the same screenshots are created in jpg format.

Because this is the comment in my example start.ini:

;screenshotformat values supported:  bmp, tga, jpg, default is jpg if not specified

png is not among the supported values, and if it doesn't match any of the supported, it will default to jpg type

(1 edit)

I just retested on 3 machines and none of them have any issue with rigging, and all use multiple core processing while at sea.  I tested a battle with 20 ships in the ERAS gold fleet and everything was fine.

Machines tested:

Win7 laptop, Intel i5 dual core, embedded Intel GPU
Win10 laptop, AMD Ryzen 5, Radion R4
Win10 desktop, AMD Ryzen 3, GTX 1060

I can't fix what I can't reproduce on my own machines and none of them have this problem you show and all of them utilized multiple cores to distribute processing.

(2 edits)

There are problems running on revisions 196-197.

The game just won't start.

Where can we find the error in the scripts? All your mods run without problems, but it is our modpacks that cannot run.

(+1)

Version 200 did not fix the crash bug completely. However, the game manages to load before the main menu and crashes.

Version 201 still didn't fix that issue. My custom modpack crashes randomly inbetween ending of initialization to 1 second in main menu.

Same problem on 200 and 201 versions

It works for all except anything Leopard provides because he is distributing Maelstrom elsewhere on the internet.