madvad

OFFtopic: The ArmA series is the game of my life. I started with Operation Flashpoint, then I moved on to ArmA2+OA, where I have thousands of hours, created mods, servers... for me, it's the perfect MilSim game. When A3 came out, I bought all the DLCs and was super excited, only to be deeply saddened, because, in my opinion, they ruined the game. The graphics were obviously a huge improvement over OA, and the Workshop was an innovation, but other than that, the gameplay and storyline, I found horrible. They tried to make ArmA more palatable to FPS players like BF and CoD, and I didn't like that. I went to play Reforger without high expectations, and to my surprise, it's basically an A2 brought to 2024, obviously with its limitations, after all, it's just a "test mule" for A4.

Yeah, this is what I talking about. Video cards aside, I think there is another reason for these crashes. As you mentioned, I used to run the campaign in Anatolia without any problems, and with the new terrain, and using the same aircraft, etc., I have been having crashes. I don't know if it has to do with some NVIDIA update, there was one of them that my game didn't run at all, I reverted to the previous one and it worked. And today with the latest driver, it works as well. I know that my video card (1050Ti) is far from powerful by today's standards, but I don't consider my machine that bad (I5 from not so old generation, 16Gb RAM), and I run several current games with graphics set to good settings without any problems, such as ArmA Reforger, GTA V, Assetto Corsa and others. Another example is my notebook, with a 3GB video card that used to run smoothly what I can't run today (like ODS 30Th for example). For example, the "Iraq 80" and "IraqWA" maps from ODS suddenly stopped working, even though I had already reinstalled them and done everything. "Iraq 03" and "IranIraq" work fine, just like the GermanyCE (you mention doesn't work for you, it's ok for me). I have the impression that something is corrupted, I don't know... I still don't understand... :)

Yes, but apart from that SF2 itself has a problem related to the allocated memory hash, and it crashes after some missions. If the mods are getting heavier and heavier, what are we going to do?

Well, that's what I believe. Missions with large maps full of details like Anatolia are a matter of luck, they often crash. I remember that in the past everything ran without any problems, but then I also remember that in the past there were no mods with textures of such high quality. When I see that the mod has very high textures, I convert and reduce them to 2048 or 1024. But...

Guys, analyzing the reason why sometimes my game crashes at 80% of loading, and the reason appears to be something related to directx10.dll (even though I have a 4gb video card, which I consider OK for an old game like this), I went to take a look at this flightengine.ini file and found some entries that I would like to know what they do, such as the ones I pointed out: [GraphicsSettings] ZBufferDepth=24 MaxVertexCount=16384 MaxIndexCount=98303 MaxTextureCount=4096 MaxModelType=2024 //MaxModelType=2048 MaxMeshPerScene=4096 //MaxLightPerScene=256 MaxLightPerScene=512 MaxModelPerScene=2024 //MaxModelPerScene=2048 AspectRatio=1.333333 MinPixelSize=1.0 [UnlimitedDetailOption] HorizonDistance=62000.0 //HorizonDistance=70000.0 DetailMeshSize=11 DetailLevel=2 WaterEffect=2 NoiseTexture=1 //MaxTextureRes=-1 MaxTextureRes=3072 The ones that are listed as commented // I probably copied them from someone over the years, but to be honest, apart from the obvious ones, I don't know what they improve individually. And if anyone has a file like this that allows some improvement in the game, or even that fixes what might be wrong with mine, I'd appreciate it.

Looks like the file is updated, awaiting aproval.

And yes, I returned to base. Just need to change my underwear and was ready to fly again

To be honest, I've tried using a wrapper to try to mitigate this, and it didn't do anything. It's frustrating. Thanks for you help, as always.

Hello everyone! I'm experiencing a crash during loading in some specific terrains, as follows: IraqWA 80-03 version (IraqWA03 works OK) IraqWA ODS30 version IR2003 All other terrains runs perfectly. Strangely, the previous versions of these maps worked without problems, but the latest updates started giving me this error. My machine is a penultimate generation I5, with 16GB RAM and an Nvidia 1050Ti 4Gb. I run games much heavier than the merged SF2:NA without any problems. I've already reinstalled everything, I've already changed the graphics card drivers... I always get an error related to this path: C:\Program Files (x86)\ThirdWire\Strike Fighters 2\Core\GraphicsEngineDX10.dll Could this .dll in my installation be corrupted? Could someone send me this specific dll so I can test it?

The invite is expired/inválid. In your linketree too.

Foxbat!

So I can assume that the .lods included in ODS 30AE are a upgrade over the standard ones available in CA as a single download?

Take care my friend! Wish you all the best!

I fixed the campaign. It is a edited version of the Operation Pelayo, available in the downloads section. If someone want to try it: OP_Pelayo_1987.ini OP_PE_Data.ini

I fixed this comparing the cockpit position with the A-6A '69 previously released. And the correct entrie to fix this are: //Position=-0.350,2.550,0.740 Position=-0.350,3.0,0.795 <<<<<<<<<<

This happens due to a bug generated by the Campaign editor. To solve this, take a unit that is controlled by the AI, that is, that does not have the option of being piloted by you, put this unit in a new entry of "[AirUnitxxx]" and put the aircraft/squadron etc in the place of the old one. It will work. And to be able to fly in the enemy nation, you can keep the entries where they are, you just need to take into account that the "AirUNITS" count starts from 0 on the "red side".For example, a MiG is there as "AirUnit086" in the general sequence in xxxDATA.INI file, but if is the first entry in the "other nation", in the xxx.INI file she need to be UnitID=1, if it is the first enemy aircraft in the sequence. Do the count taking into account the sequence in which they appear, instead of the sequence in general, by adding these entries in the xxx.INI you will be able to fly on the enemy side without any problems. I will add here my Rolling Thunder campaign with several entries that I made as example: CAMPAIGNV1.INI CAMPAIGNV1_DATA.INI

It was exactly like this, and I followed all the steps. I download the original SF1 map and subscribe the old files with this new files, but not sucessful. But thanks for your tip!