AoP2 GoF 2.1.5 (Beta) CTD during Rain/Storms

[GHOSTMD]

Hey guys o/,

has been a while aye? But i found back to playing AoP 2 GoF Mod
just a week ago *smirk* Good to see Pirates Ahoy is still alive.

Ok why i post this, is just the simple question if anybody has a workaround
for the CTDs during storms / rainy weather?

Game itself seems running pretty stable on my RIG

Xeon 1241v3, 16GB RAM, GTX980; Asus Maximus Hero VII
Win7 Ultimate (64 Bit)

Install folder:
D:\Spiele\AoP2

During "normal" gameplay AoP 2 is just running fine.
Just very seldom, when it rains the game crashes, with the usual engine.exe
warning. But the really annoying part was the COAS questline.
Starting phase constant CTD when i tried to get to chad.
Ending phase, after i talk to the mechanic and have to recruit the ppls
around the town... game crashed every 30 secs. Certain effect of the rain it seems
since the time till the crash differs.

St Augustin and on Tatarus the game runs stable... no matter what weather COAS
has. Also on sunny days game is stable...
Endphase, when you re on the Tatarus again (after recruiting) game is also
stable again.

I "buged" myself through it, but was pretty annoying and frustrating.
I made some changes to certain ships so i started a new game.
I want to avoid the frustration this time. SO is there any help with
this issue? Specially for the COAS quest?
(for example changing the weather constantly there?)
except for the endphase Tatatus >>> Diffindur?

Enabled Debuginfo... but AoP2 doesn t seems to write the error.log
That is just weird...

I hope someone has a tip for me how to avoid that BUG.

Thx

BTW Guys
I look forward to Hearts of Oak, good work and keep it going.
We have to few Pirate games.

 

[Hylie Pistof]

Every once in a while someone complains about CTDs in rain/storms but I have never experienced it. But the biggest issue is that no one who could fix it is still around.

 

[GHOSTMD]

Little update,

got the error logging to run, forgot the enable the filetracing.
Let's hope the log files can lead the way.

So far it seems AoP2 GoF mod used a certan Rain tech twice...
also several error msgs with "palms" in the COAS there are none
(geometry model load fails)
Same for some Waves also geometry model loading fails...

Still now i had no crash during rain, while the logs are running.
Lets see what they say when the games has the next "rain" crash
to desktop.

@Hylie Pistof
You did not even had a crash during the COAS quest? When you walk
through the ships? ... damn... spit out your dirty secret, right now!

 

[Hylie Pistof]

Err umm, I never got close to completing that quest. I wandered around on the ships a bit but never got anywhere as I have never completed some other quests that have to be completed first.

In regular game play I have gotten CTDs but they happened in big battles that just overloaded the game engine. The big problem for me is that sometimes when a lot of enemy ships approach the frame rate counter will say it is getting 60 fps but it looks more like 5 fps. The action just stops like a screen freeze.

 

[Galleon Love]

There is a fix for the Tartarus glitch in the COAS quest, however it cannot be found on Pirates Ahoy. I would suggest using google and entering the following text: Like others have complained, when I left the Tartarus, game is stuck, you are on deck, not in water. But, knowing there was a problem, I saved just prior to opening the door. We also got a handy error in the log at that moment:

If you do this you will find the solution fix and it is very easy to implement.

¡buen viaje!

Hey guys o/,

has been a while aye? But i found back to playing AoP 2 GoF Mod
just a week ago *smirk* Good to see Pirates Ahoy is still alive.

Ok why i post this, is just the simple question if anybody has a workaround
for the CTDs during storms / rainy weather?

Game itself seems running pretty stable on my RIG

Xeon 1241v3, 16GB RAM, GTX980; Asus Maximus Hero VII
Win7 Ultimate (64 Bit)

Install folder:
D:\Spiele\AoP2

During "normal" gameplay AoP 2 is just running fine.
Just very seldom, when it rains the game crashes, with the usual engine.exe
warning. But the really annoying part was the COAS questline.
Starting phase constant CTD when i tried to get to chad.
Ending phase, after i talk to the mechanic and have to recruit the ppls
around the town... game crashed every 30 secs. Certain effect of the rain it seems
since the time till the crash differs.

St Augustin and on Tatarus the game runs stable... no matter what weather COAS
has. Also on sunny days game is stable...
Endphase, when you re on the Tatarus again (after recruiting) game is also
stable again.

I "buged" myself through it, but was pretty annoying and frustrating.
I made some changes to certain ships so i started a new game.
I want to avoid the frustration this time. SO is there any help with
this issue? Specially for the COAS quest?
(for example changing the weather constantly there?)
except for the endphase Tatatus >>> Diffindur?

Enabled Debuginfo... but AoP2 doesn t seems to write the error.log
That is just weird...

I hope someone has a tip for me how to avoid that BUG.

Thx

BTW Guys
I look forward to Hearts of Oak, good work and keep it going.
We have to few Pirate games.

 

[Thagarr]

I would suggest that anyone planning on following Galleon Love's advice should use a good proxy server, and make sure your security suite software is up to date.

 

[GHOSTMD]

another little update guys

no rain crash yet, but it is only a matter of time.
System.log shows several gm file loading fails bound to iland waves and palms.
also several texture loading fails shown (don t know if it is normal for GoF Mod)
But i doubt... i definitly need someone who is into Storm Engine Coding here i think.
Also a sound channel "collisions" is shown there, as soon as i get a RAIN CRASH
System.log i ll attach it here... hope you guys can get me some hints to fix the problems.

@Galleon Love
Tatarus part works just fine! (as i wrote above) St Augistin and Tatarus the game runs stable no matter
what weather is "played", during the COAS quest i only get the CTDs around THE PLUTO.

Most annoying part (also written above) was the recruiting people for the Dog of War, since you can
not avoid the stormy weather during that quest phase... after that the game runs stable once i get to
the Tatarus again. So endphase is just fine.. no need to search a fix for a glitch i do not have.

 

[GHOSTMD]

Ok got sick of waiting for a "normal" rain crash, so i ported my char to the COAS "iland"
via DebugWindow.

as expected after talking to Stoker, game crashed when i tried to get to chad aka try
to cross The Pluto. (starting phase of COAS with starting "Storm") here are the logs i
got. Hope one of the GoF Modders or Coders can give me a hint here.

several texture loading fails and sound fails in the system log, then this:
ERROR: SetCurrentBlock: unknown technique <> first character is <(null)>
LockIndexBuffer::LockIndexBuffer
Undefined error
Assert failed in .\WaterRings.cpp line 144, expression string _iPointer

on time the games crashes, so as predicted the engine fails when a certain effect is called.
unfortunatly i am just a IT Admin not a coder/scripter so can't get much out of it.
Except for some missing files in the game folders.

 

[ChezJfrey]

I would suggest that anyone planning on following Galleon Love's advice should use a good proxy server, and make sure your security suite software is up to date.

I have seen several of these 'warnings' and I'm perplexed. I have been there many times, without issue...it's just a typical web site hosted by a 3rd party, with Wordpress tie-ins.

Plug it in here: Safe Browsing Site Status – Transparency Report – Google

Google’s Safe Browsing technology examines billions of URLs per day looking for unsafe websites. Every day, we discover thousands of new unsafe sites, many of which are legitimate websites that have been compromised. When we detect unsafe sites, we show warnings on Google Search and in web browsers. You can search to see whether a website is currently dangerous to visit.

Current status:
Not dangerous
Safe Browsing has not recently seen malicious content on <sitethatshallnotbenamed>

As for the rest of Galleon Love's mention, I'm sure that particular bug was unrelated, as GHOSTMD asserts; I'm certain that Tartarus issue was solely in a different mod (and now resolved) that shall not be named, not GOF 2.

 

[Thagarr]

@ChezJfrey, I dunno about you mate, but I certainly do not trust Google to tell me what sites are safe on the Internet. There are many ways to attack a browser that bypass security suits all together, and that number is growing every day. Data-mining is everywhere now, in many different forms. I wouldn't post a warning like that without good reason.

 

[GHOSTMD]

Greetings

Ok guys i tracked down the issue, i am 95% sure it is not the GoF 2.1.5 Mod
neither it can t be the GoF ERAS "extention" i tried several "instances" of GoF

In every "fresh" AoP2 + GoF mod installation, i get that WaterRing.cpp line 144 error
in the System log... so seems to be the good old NVIDIA GPU Bug
Anybody remembers a workaround? Or the correct configuration?
I believe there was something, that solved this particular issue of AoP2 with NVidia cards.

So long

 

[JP Jones]

Need to disable rain in the game completely.
Edit the WhrRain.C file in the PROGRAM/Weather folder
Find these lines at the end of the file:

void MoveRainToLayers(string sExecuteLayer, string sRealizeLayer)
{
LayerDelObject("execute",&Rain);
LayerDelObject("realize",&Rain);
LayerDelObject(SEA_EXECUTE,&Rain);
LayerDelObject(SEA_REALIZE,&Rain);

LayerAddObject(sExecuteLayer, &Rain, 65537);
LayerAddObject(sRealizeLayer, &Rain, 65537);
}

void ShowRain(int bShow)
{
SendMessage(Rain,"ll",1,bShow);
}

and change to:

void MoveRainToLayers(string sExecuteLayer, string sRealizeLayer)
{
// LayerDelObject("execute",&Rain);
// LayerDelObject("realize",&Rain);
// LayerDelObject(SEA_EXECUTE,&Rain);
// LayerDelObject(SEA_REALIZE,&Rain);
//
// LayerAddObject(sExecuteLayer, &Rain, 65537);
// LayerAddObject(sRealizeLayer, &Rain, 65537);
}

void ShowRain(int bShow)
{
SendMessage(Rain,"ll",1,bShow);
}