UllyB

View File MirageIIICJ_Shahak_Loading_screens 2560x1440 This is a pack for people who want diversity when it comes to an aircraft loading screen and use a UHD monitor which can handle 2560x1440 resolutions. This pack is designed for the Israeli Mirage IIICJ Shahak. I was inspired by the "Six day warriors" Deuces work. Instructions: I made this pack for the SF1_WOI game but it should work with the other SF1_X games, as well. Just unzip the pack and choose a picture you like. Change its name into Shahak_Loading.bmp and place it into /Wings over Israel/Objects/Aircraft/Shahak/ folder. That's it. Start the game and when the game will load the mission, presuming you will choose to fly a Mirage IIICJ Shahak single player random generated mission, you will see this screen. I hope you will enjoy it. You can use my mod in your projects but you must add me to the credit list. Submitter UllyB Submitted 07/05/2016 Category SF/WO* Hanger/Menu/Loadout

I took a look to the link. Viper63 made changes for SF2 series I understood. I was asking about SF1 series loading screen stuff. They are different made, in SF1 they are bmp, in SF2 they are jpg or something. Anyway I wrote to him a PM. I hope he will help me in the end to discover what I am doing wrong. Thank you for helping.

I recently bought an UHD resolution pc monitor and I would like to upgrade from 1920x1080 to 2560x1440 resolution, the default bitmaps for loading screen, menu etc but they won't work. I made custom bmp files, in 2560x1440 and saved them as BMPs (24bit) and then replace them all, changing the bmp file name accordingly of course, but they are not displayed or they are displayed wrong. Where is the mistake I made please? I really need help.

if it would be the PSU the pc would suddenly shut itself or would reset the pc, but not entering in sleep mode. I never seen a PSU to cause that in 20 years of experience. More likley the video drivers are corrupted or a faulty monitor.

so if I get right, its role is to prevent AI planes to appear where they shouldn't, right ? Cause flyable planes it's already clear that have nothing to do with that file. But I dont' understand a thing, now that I remembered about data .ini plane's file. In it there's already an END date for that plane (AI plane I'm talking about now) and that AI plane can't fly , let's say the end year is 1980, past 1980, right ? So in that case userlist.ini seems redundant or am I missing something ? And that it's available for all SF series, they all have files with AI planes in it , which have a start and an end date for it.

"undocumented I meant that the respective line is not there in the file, in an ordinary, stock etc. Or at least I never saw it in stock or 3rd party files. I'm sure I would have remembered it it I did.

lol...you gotta be kidding me...TK doesn't speak with my kind, he doesn't have time for chat. I never saw him on this site in threads or maybe I don't know his nick. I just asked those matters because I thought that who played a lot SF2 series knows well the ropes and knows things in details. Me who I played a lot SF1 WOI I can talk about every detail and trick I learned in all these years. Modding little things like menus, skins repainting, tweaking FM etc all these means experience and knowledge, as you know, is the real power. Some things I discovered them myself or I had lots of moments of revelation about things relating to this sim. I remember, In 2002, I was looking for a military flight sim and this way I ran into TK's sim. Well, it's not F-22TAW value yet but it has a bright future. If DID didn't abandon games area, companies like Novalogic, Eagle Dynamics or anyone else would never have existed, that good their sims were, but maybe you know that if you are old enough and played it. When you played something really good, you never forget that taste in your mouth....and you tend to compare everything with it.

I forgot an aspect, it's not incompatibility at all.The model is old. No connection with SF2 series whatsoever. I barely made it not wobbling on the runaway, lol. First time when I used this exploded on the runaway beacuse of bouncing...lol...I changed some data into the gear section and it worked fine, a sort of speak...

Well someone older in SF2 matters maybe will enlighten me a bit here. What I understood reading about this new feature userlist.ini was this: What happens in this situation: - operational theater WOI/single missions - the aircraft is let's say Lybian (Mirage 5D) - I have two skins , both under Libya flag - Egypt, in user list used this aircraft between 1971 and 1974 - Libya used it between 1971 and 2020 (well it's not 2020 yet , but you know what i meant) In this scenario I thought that IF I choose the plane and choose then Lybia as country from the list, I will see the year list between 1971 and 2020. Similar, if I choose Egypt I thought I will be able to use it just between 1971 and 1974, but for Egypt you can use it until 2020. as well. If the list doesn't limit anything according with the years each country use it in that file, then what is the point of that file ? Furthermore , it seems I can play with it under any flag found there in the list. Is the file in relationship with data.ini file interval only .or in single mission it doesn't work ? How does it work actually, I don't get it ? (And YES , I read the KB, otherwise I wouldn't be here now writing this post.)

thank you, that's nice of you :)

The orther MIG-23 are ok, their animation is complete. First after integrate them into your SF1 version, check this: Choose a flight with 4 planes at least, if it is you and your wingman the issue it won't appear. Look closely (press F6 to select that particular plane you are watching) for each plane how is taking off. You will see no issue. After that refly the mission and don't look back :), just stay in your plane's cockpit until ALL the other three planes took off. After that look to No 3 and No 4. You will see the issue. The funny part, still unexplainable, is when you have MORE than 4 planes. Try with 8 planes and the anomaly will take new forms. The first flight will not exhibit the anomaly but the last two or three planes from the last filight will do. The crazy part is that you can repeat this "scenario" until you don't know what your name is and...the results will be the same which is mind blowing...lol If you help me solve this I would be grateful. Here's the link to the files: http://www58.zippyshare.com/v/97242077/file.html

My SF1 WOI works great in Win7 x64, even in ProgramFilesX86 ..lol (yeah I know I shouldn't , it bothers me everytine with aproval when i wanna change something in it, but I got lazy lol), you just must set the compatibility with Win XP SP3 and have that patch from oct 2008, that's all

I agree but, now iit is not 2002 anymore. TK's sim made a step forward to a BETER one with the SF2 series so the expectations are greater, too. The Red Crown thing must disappear at least form WOI and other places where it doesn't belong. The argument that this thing doesn't have impact to the gameplay doesn't stands, from my point of view. It is as if I am in a restaurant and eat my meal and in the lobby there are two cows, Of course , I can eat with two cows in the lobby but, they don't BELONG there. With the fame you earn creating a very good thing comes the RESPECT and RESPONSABILITY for everything you put in it so...the polishing must never stop. Maybe some wouldn't agree with me, it's their right, but this is my opinion and I felt I had to present it. I hope I didn't bother any pride.

Oh, I see...Undocumented maybe, I didn't see it in decals.ini file, otherwise I would have thought about using it. Thanks for the tip

it worked, thank you once again, now I can see all the map in one sight. This was a good tip.

1.If you press Y key , to see friendly aircraft which are very near and IF....that particular selected is havin a high speed (from 0.9 mach up) the interface will show, IN THE SAME TIME, his speed in kts and in mach :), but ALL in the same "sentence" if you know what I mean :D., and you can't see anything clear because of that. 2. It seems that the red crown (awacs or what it is) "knows" where the enemy is , even if it didn't start any engine. If you ask red cron for threats, BEFORE the target aircraft are airborne, it will reply: "multiple bandits, 50 miles , angel (and now come the best and laughable part) ZERO, heading north !...lol So , translating it would be : "they didn't yet take off, but they are on the runaway , facing north", which is too much even for an USA AWACS...:) I got this when I was flying a Mirage 5D and I was heading to Israel south border. In my opinion, this red crown thing should be erased, at least when you play with arabs aircraft, they didn't have AWACS in those times if I remember correctly. I think not even the Israelis didn't have airborne control in 67. But I remember they had one in 1976 (Entebbe job). I know that this red crown is from WOV times and never got off. Maybe it would be nice if TK and the gang would make a real AWACS and all the commands would work.

wow, thanks man, I think that is what I was looking for.

well I put all the MIG-17s to 1 and play to see what it happens....and , of course, as always, I will let you all know :)

tweaking some skins to work with SF2 series (it's a nightmare, by the way) I found an error, in fact more than one, but the type of error is the same. Algeria , if you noticed, doesn't have a "symetrical" flag. So...the decals, as TK fixed them (or whoever did it) look wrong, the flag on those particular skins is backward. So, for MIG-17F, instead of the sequence: [Decal001] MeshName=Vert_Tail DecalLevel=0 DecalFacing=RIGHT FilenameFormat=FinFlashR Position=-3.87,0.95 Scale=1.8 DecalMaxLOD=3 [Decal002] MeshName=Vert_Tail DecalLevel=0 DecalFacing=LEFT FilenameFormat=FinFlashL Position=-3.87,0.95 Scale=1.8 DecalMaxLOD=3 the correct one is: [Decal001] MeshName=Vert_Tail DecalLevel=0 DecalFacing=RIGHT FilenameFormat=FinFlashL Position=-3.87,0.95 Scale=1.8 DecalMaxLOD=3 [Decal002] MeshName=Vert_Tail DecalLevel=0 DecalFacing=LEFT FilenameFormat=FinFlashL Position=-3.87,0.95 Scale=1.8 DecalMaxLOD=3 The same goes for the decals with the flag on the fuselage: Instead of: [Decal007] MeshName=Fuselage DecalLevel=0 DecalFacing=RIGHT FilenameFormat=InsigniaFuseR Position=-1.52,-0.16 Scale=1.5 DecalMaxLOD=3 [Decal008] MeshName=Fuselage DecalLevel=0 DecalFacing=LEFT FilenameFormat=InsigniaFuseL Position=-1.52,-0.16 Scale=1.5 DecalMaxLOD=3 the correct one is: [Decal007] MeshName=Fuselage DecalLevel=0 DecalFacing=RIGHT FilenameFormat=InsigniaFuseL Position=-1.52,-0.16 Scale=1.5 DecalMaxLOD=3 [Decal008] MeshName=Fuselage DecalLevel=0 DecalFacing=LEFT FilenameFormat=InsigniaFuseL Position=-1.52,-0.16 Scale=1.5 DecalMaxLOD=3 I bet the error repeats for all flags that are not symetric. If I will encounter any I will post again. I hope that helps SF2 to be a better/complete game. I found these in SF2: WOI , for the MIG-!7F

Please read my post ..again :). I asked what is hapening if I put ALL the skins to default 1. I didn't say anything about any...date so your example doesn't, unfortunately, cover the..."topic" :)

what happens if all the skins in ini file have StartDefaultDate=1 ? I noticed that some aircraft had that parameter fixed thatway for more than one plane in the ini file of the aircraft. Does that mean that skins will appear randomly and not just the default one as in SF1 series ? I'm talking about single missions. It would be great to be thatway but it's too good to be true I'm afraid...

As you already noticed the ingame map in SF2 offers a bigger view than the one in SF1 series when you zoom it out. I thought it's the resolution of the map itself , but it isn't. So I figured that might be some settings in an ini file of the terrain or...the game's engine "knows" to make it bigger when you zoom it out. if anyone knows, please, can this be "exported" for SF1 as well or am I beating a dead horse here ?

I already have it. This one is made in 2004 and it is my No1 , too, in my list. However I've got two more....:D