Menrva

I remember YEYEYE had a personal website, I recall I downloaded incomplete Su-47 and X-32 models for Strike Fighters from it. I don't recall anything about a Su-24 cockpit, I'm surprised it found its way somehow without a public release. If the plane and cockpit can be released with due credits to the authors, I'd be happy to include this new Su-24 in the ODS 30AE mod as a flyable aircraft.

That cockpit's 3d modeling and texturing style... it reminds me a lot of cockpits created by YEYEYE, maybe it's from him? I don't know. No idea where this Su-24 model comes from, I'd be happy to know if it's something legit that we can use.

I'm terribly sad to hear these news. It's been a while since last time I heard from Marty via email... I'm as shocked and saddened as much as I'm honored to have known him. One of the kindest men I've ever known. I'm keeping all posts from him with care. Our chats and his positive posts and comments made my day more than once. I lack the words to truly express how I feel about this loss. My deepest condolences to his family and loved ones, and to the guys of the CombatACE community who, like me, had the pleasure of chatting and collaborating with him. Rest in peace, Marty.

You need a GPU with at least 4GB VRAM. The mod does not work on Intel UHD integrated graphics cards. I already posted all possible suggestions and solutions to known issues in the mod's download page.

These are unused but working BlendOp options as found inside the GraphicsEngineDX10.dll: MODULATE_AND_ADD_SRC MODULATE_AND_ADD_DST MODULATE_MUL_2 MODULATE_INV_SRC MODULATE_INV_DST My discovery was dictated by my hunger of finding a proper solution to the DTV filter which does not work properly in-game with night environments, especially with the much darker nights of my realSKY mod. Below you'll find a comparison between stock filter material data and the custom one using another BlendOp: Stock MODULATE, day Stock MODULATE, night Unused MODULATE_MUL_2, day Unused MODULATE_MUL_2, night The main drawback of MODULATE_MUL_2 is that it doubles the MODULATE option, so at day the image is lightened too much than the stock MODULATE. Mind you, the screenshots were taken with the realSKY mod on Unlimited settings, so the post processing effect adds bloom to already bright areas. However, at night MODULATE_MUL_2 brings a big improvement as you can finally see the ground and its objects more easily. PS: Please admins, pin this topic. The unused BlendOps I found work just fine, and may be useful to other modders willing to experiment with them.

Posts like this mean a lot, believe me. We modders create so much but we rarely get any feedback after dozens and dozens of downloads. Glad to hear your voice, you're welcome!

You're confused about WoE. The first generation of Strike Fighters games never had sounds for chaff and flares. Strike Fighters 2 never added them either. Sounds are probably the worst part of Strike Fighters. If you're hit, deploy countermeasures or drop bombs, there's no sound associated with those events. Nothing we can do, it's another limitation of the game engine.

The Su-22M4 cockpit by Farid is nicely detailed! It just misses a working mirror glass on the top, centre strut of the canopy. It'd be awesome if Farid could add that and even make the M3 cockpit by reworking the M4 one. Strike Fighters very rarely gets new cockpits these days, so I'm thankful for this addition.

It's not clear what the file exactly does but it does not seem to have any visible effect. The game already knows if a target area is Friendly or Enemy and in which specific Location thanks to the _targets.ini and nations.ini files. Even if we understand how this additional file works, we'd know colors only for a limited number of nations. On terrains having more countries, who knows which colors are exactly needed for that file. Simply put, I'd move on.

I think everyone using mods and not having a PC with NASA specs has the issue. Never managed to find an exact cause apart from the game's management of VRAM; it's also random, doesn't matter which weapon, even with the same one, sometimes it's an issue, sometimes FPS is decent. I'd classify it as a stock game engine issue, nothing that could be fixed. In the stock game it won't happen, but as soon as you add mods, custom effects, custom terrains and/or a third-party aircraft, then it happens.

My condolences to you and your family. My thoughts are with you all.

They must add this kind of mission as well in MSFS 2024: https://www.instagram.com/p/Csz3-eDrPca/?igshid=Y2IzZGU1MTFhOQ== Airlifting cows with a helicopter from Swiss mountains to the vet.

@orsin There's another experiment using TODs and tweaked shader done by Stary for his Korea/Taiwan tileset. Basically the texture for TOD buildings would be a TGA and windows would be made transparent. With the tweaked shader Stary provided, windows wouldn't be affected by darkness and would be visible from a long distance, thus simulating lit interiors of the buildings. There's one major issue with this approach; you'd have to set ObjectsFade=FALSE in the Options.ini and MipMap=FALSE for SolidObjectTextureMaterial in the terrain's data.ini or else it won't work at all, and by doing so you'd get lots of very noticeable flickering which cannot be fixed. Mip mapping exists for that exact purpose and so disabling it is not ideal at all. With either mip mapping or fading enabled, this trick by Stary no longer works. This would be the best solution if the flickering could be solved somehow, but mip mapping is a necessity.

It can be done, but each city has its own size and tiling so many variations might be needed. The object requires to be set up as a ground object (as a downside, it would appear in the mission editor), not placed as a terrain object because the light effect would flicker very much otherwise. I know this since me and Jimbib added floodlights to new airbases made for the ODS 30AE mod, together with a light effect. Speaking of which, I haven't thought about using horizontal polygons for the light, we can simply use SF2's effects to create such lights, as done already on carriers and vehicles of the ODS 30AE mod. About making them destroyable, the way the game works, you'd have to make each lamp post separate sadly. Make one huge object with 50 of them and destroying one would destroy them all. All in all, it's worth a try, but there are side issues and limitations to take into account.

Nope, it's just the HUD texture that was given a green color and it makes darker areas more noticeable in-game, it's just a normal consequence to our eyes, there's a deeper scientific reason as to why green is used in real life for NVGs. The effect of the green on the HUD texture also depends a lot on the quality of the screen panel on which you play games. On my end, without cockpit, I couldn't see the terrain on the horizon at night with the realSKY mod. By enabling the cockpit, then I could distinguish the terrain from the sky thanks to the HUD's reworked texture. There is no way to add such a FLIR shader effect to the 3d model of the cockpit. Hell, we don't even have a proper FLIR shader in the game for the DTV in cockpits, which is the cheap reason why TK made nights unrealistically bright. We've been there already, we've been modding the game for two entire decades (considering SFP1 days) so we know all about the engine limitations, there's nothing new to discover about it. The only realistic solution (apart from using Unlimited Effects, thus having TW's post processing shader kick-in all the time) is to use a shader injection method like Reshade, but that one eats a lot of resources and can decrease FPS by a lot depending on the system on which you run it. I've been looking for lighter alternatives but nothing good that works in SF2 so far. All that is needed is to reproduce the shader done by simonmiller416 for use on such a shader injector (the TW .FX shader cannot be re-used as is, the shader injector usually requires its own syntax and/or language).

You can select and hide nodes in LODViewer as well before taking screenshots, it can be a useful function in this case. Keep up the great work, this is an awesome project! We could make some time trial missions on the smaller NL terrains I released a while ago, if only we had proper towers acting as route checkpoints.

A small island in the Gulf for a friend...

Hey Eric, I wasn't referring to you, so don't worry! Also, things like these tend to happen, RL these days makes us do everything faster. I'd lie if I say I have never read a post in a hurry without misunderstanding it. No worries, mate, it happens. Also, daddyairplanes pointed out a good reason, the pic I uploaded was certainly distracting. The most important info wasn't given a clear space in the post I made, so this is my mistake as well. Looking forward to seeing what you'll do with those textures, it must be an interesting project!

Thanks for noticing it. I don't know why, it's not the first time that my posts seem to be ignored or not fully understood by other users of the site. On another recent topic I suggested some solutions, but the user in that case missed it or rather focused on another post that didn't provide a solution. I'm truly wondering if something's wrong with my English, it is not my mother language

They are in ObjectData001.CAT, thanks to mue's LODViewer I got the list of textures: A-4B_pit_textures.txt Use his CAT Extractor and you can look for each single texture.

The post processing effect is applied also in daytime, so it's not an optimal solution. Only with injectors like Reshade it's possible to make something that works on a specific key press. SF2 remains very limited in how stock post processing works.

I may be wrong, but I think @Cliff7600 is the only FM guru still around. Baffmeister hasn't been around in a long time, he contributed for some time on ODS 30AE. Both are very talented! I have no such good knowledge on flight models.

The crap is yours I'm afraid, unless you believe John and Mike are still alive, cause they aren't. And the guy working on YAP-RW is an end-user (not a 3d modeller nor a modder) who bought those products. Is he at fault because he updated the products he bought for use on SF2 for free? He also was scammed if the stuff he bought was stolen and that's terrible. I don't think anyone can held him responsible for the crap done by others. That's what I meant with my post. The RW guy, unlike the original YAP guys, is at least asking for permissions in using CA mods in his rework, and he's also crediting modders. Original YAP never did this to my knowledge, they'd rather steal and monetize upon free mods. Before disliking posts trying to give a more complete perspective of the situation, think twice. I (luckily) never dealt with YAP in the past and I never cared about it. I'd obviously be angry if any of my work had been monetized by others. I'm here for creating and sharing free legitimate mods. If you had an issue with YAP in the past, it's your problem that you haven't solved it in years before the owners died. You're a nobody to call me a liar, and it's suspicious this is only your fourth post on CombatACE. Your previous three posts were about complaining that GKABS' 3d models don't work on SF1. You've never contributed anything over here from what I see, you behave like a troll. You'd rather show some respect to people in the community.

Just to clarify, it's not the YAP most over here at CA think it is. YAP-RW is a free fan-made project done almost entirely by one end-user who bought all YAP products in the past; he's been updating those so that they work on Strike Fighters 2 for his own enjoyment and simply thought about sharing what he's done for free. He's in no way related to the original YAP nor to the fact original YAP guys monetized upon freeware mods without permission. The owners of YAP died years ago and the store was still up despite not being controlled by anyone anymore. Apologies for the little off-topic, it's just that I've seen people complain about YAP-RW as if it was done or even monetized (it is not) by the same YAP guys responsible for those issues. This is a case where an unrelated end-user was held accountable by some for the issues surrounding those products, products he legitimately bought without knowing of all this chaos.