Jump to content

Recommended Posts

Where can i get a mod for Hal Tejas. any suggestion.

Edited by Anshuman

Share this post


Link to post
Share on other sites

Sadly there is no Tejas available for Strike Fighters 1, WoX series.

Only for strike fighters 2.

Share this post


Link to post
Share on other sites
On 11.05.2020 at 12:47 PM, Anshuman said:

Where can i get a mod for Hal Tejas. any suggestion.

Hello!

You can download the Hal Tejas airplane model here.

 

The plane works (!) in 1st Gens, although minor modifications will be required. First of all, save the main Banidos_Tejas file in the ANSI format instead of Unicode, otherwise the game simply will not see it. Please contact if you have questions.

Edited by Crawford

Share this post


Link to post
Share on other sites
On 11.05.2020 at 12:47 PM, Anshuman said:

 

By the way, here is a small SkinPack for this aircraft:

 

 

Share this post


Link to post
Share on other sites

Thanks Brother,but currently i m playing WOE, i v already downloaded the previous file u mentioned ,but its not working in WOE.i ll try this too

Share this post


Link to post
Share on other sites

bet it's a unicode lod... they don't work in 1stGens, and the game engine can't "see" them.

 

Share this post


Link to post
Share on other sites
2 hours ago, Wrench said:

bet it's a unicode lod... they don't work in 1stGens, and the game engine can't "see" them.

 

:no: You will laugh, but THIS lod is written in ANSI, so it works great in the 1stGens. I guarantee it. ))

Probably, at that time Banidos was still using a normal MaxExporter_Max2009 without newfangled bells and whistles. In general, there is no difference if you do not use bump maps. Unfortunately, this beautiful model has a well-known shadow bug, so it’s better to turn off shadows in the main Banidos_Tejas.ini file.

5ec6f7ee42c61_HALTejas.jpg.54bf1496591704298ccbb35d490f7e75.jpg

By the way, a 100% sure way to determine whether the mod will work in 1stGens: just open the LOD file using Notepad (suddenly). If the opened text begins with the letters L O D , then the file is written in Unicode and 1stGens series games will not see it.

  • Like 1

Share this post


Link to post
Share on other sites

that is one of the WORST shadow bugs I've ever seen!!!

I didn't know about Notepad. I've been using a hex editor to open lods since the early 2000s!! Ya learn something everyday!

  • Like 1

Share this post


Link to post
Share on other sites
On 22.05.2020 at 2:54 AM, Wrench said:

I didn't know about Notepad. I've been using a hex editor to open lods since the early 2000s!! Ya learn something everyday!

We all learn something every day! :biggrin:

The focus with Notepad is good in that we can find out if the plane will fly in the 1stGens without starting the game itself. Since Mue's LOD Viewer 'sees' LODs of both formats, but does not report which format we are dealing with.

In turn, the Hex editor allows to easily change the format of textures embedded into the LODs. That is, from JPG or DDS to BMP format (or vice versa). Thus, all mods created for 2ndGens in ANSI - using MaxExporter_Max2009 - can comfortably work in 1stGens (or vice versa)).

Quote

that is one of the WORST shadow bugs I've ever seen!!!

Unfortunately yes! This bug is visible even in normal horizontal flight, and not only from some angles, as is usually noticed (when going below 45° roll).

img00017.jpg.52ce720e4e7f845392fbbd191ebb5df2.jpg

The model needs refinement in Max.
Another easy way is to just change the "CastShadow=" to FALSE. Also eliminates the problem for that single aircraft. This is not the best solution, but the only one at the moment.

Edited by Crawford

Share this post


Link to post
Share on other sites

Aleducat nunca termino ese modelo, y lo largue en beta parta que lo vuele la comunidad, por eso no me molesto en soltar otros modelos de el como el packfa T-50  

============

Google Translation (by wrench)

 

Aleducat never finished that model, and I released it in beta as the community blows it up, that's why I don't bother releasing other models of it like the packfa T-50

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Content

    • By JaneyBananey
      Hello!
      So, about a year and change ago, I posted about the horrible frankenstein of an install I used to make Wings Over Europe, the Steam version, run on Windows 10. You may be delighted and/or terrified to hear that it both runs and runs well, and is stable.
      However, I have encountered a different issue.
      I would like to fly the Hawker Hunter. The vanilla engine noise it ships with is absolutely horrible, to the point of making the aircraft unflyable. Being the spiffy little autodidact that I am, I went into the game's root folder, into the objects subfolder, and within it, tried to locate the sound folder so that I may replace the engine sounds. Yes, I checked the game's basic Sounds folder, and the engine sound for the Hunter specifically, among a few other aircraft, isn't there.
      The HunterFGA9 folder contains only three files: RAFCamo1, HunterFGA9.ini, and the .bmp image of the aircraft in the hangar. I rummaged around the .ini file to try and locate a directory that it is pulling the sounds from, to no avail. There is a reference inside of said .ini to another .ini by the name of HunterFGA9_data.ini, but I could not locate this anywhere. Clearly, it exists, as the aircraft is flyable in game, but god help me if I can find it.
      So, in the briefest possible terms: How can I replace the God-awful engine noise from the Hunter (and multiple other aircraft) with something less ear-bleed-y?
    • By JamesWilson
      Hi,
      a couple of months ago i discovered this gorgeous total conversion called "Yankee Air Pirate", and that the "REVAMP" edition for SF2 (the original one was for WOV) existed, and other awesome total conversions like "Drug Wars" and "Flight School" too, so i got ready to download them, but since i hadn't enough space at the time, i waited.
      Now i come back on the website to find out all the links and pages about the revamp are gone, there's only the original ones for SF1 series.
      Do anyone of you know why they're gone? Will they come back? They're maybe updating the mods?
      Thanks
    • By JaneyBananey
      Howdy y'all!
      So, I installed Wings Over Europe via Steam, promptly updated it to the October 2008 patch, and fixed the stuttering by using the ENB patch for Skyrim (of all things). I also cribbed the DDraw.dll from the DgVoodoo install, which prevented the game crashing when pressing escape at the end of a mission. A couple of things to note here:
      - The renderer indicated in the options menu is not ENB, but my GPU still. Despite this, the game runs perfectly fine.
      - I turned the shadows down from Unlimited to High as I read on a forum post that this could help with z-fighting, but this did not solve the issue. I will turn it back up to Unlimited if it is all the same.
      - There are absolutely no other graphical issues in the sim what so ever, no matter the aircraft, time of day, or weather.
      The issue I am describing in the title appears like so in sim. I took three screenshots so you could see the way the dark boxes flicker on surfaces. It is not just aircraft, either, but also terrain. It seems to get culled in a circle as I turn my head with TrackIR:



      As you can see, my wingman gets periodically eaten by this weird black blob. I am at a loss as to how to fix it, and if it cannot be fixed, that's completely understandable given the Biblical age of the engine. Thanks in advance!
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..