Zurawski

As I understand it... All three Talons are "slightly" different. Talon-1 appears to be the pinical of the design, while Talon-2 and -3 are older ones.

As accurate as I could make it... within the constraints of the game. I used a host of online images and and actual -1 doc. In a nutshell... it's as accurate as I could get at the time. (Could get alot more accurate now though)... Hmmm... Did I just volenteer for a side project?

Thank-You for explaining... In hindsight I owe you an apology as well. Why because I "assumed" you had detached your parts... and I also assumed you were looking for the boolean to fill the cut void (Or I would have suggested capping the objects well) Personally I cut my model after I have it completely mapped. I then hand-cut the doors, control surfaces etc by using the panel lines of the texture... Basically I like the control of where new polys are created. Boolean is okay... but it creates an ungodly amount of verts and it's decision of "where" to place new polys is pretty subject. Basicly... I find myself doing more work with boolean after the fact than I would perform doing it myself. Just different schools... nothing wrong with that! P.S. Welcome to the brotherhood of "Now I understand why new projects take so long"...

Resolved?! Do tell!... Your resolution will likely save many future modders a splitting headache (myself included).

Ignore everything I've said to this point... I'm an idiot. You do want to subtract... "subtract A-B" to be most precise. I was thinking "cut" in my previous responses. Boolean is just an inherently unstable modifier... One can do 100 projects with no boolean issues and others can't ever get it to work properly. I've personally noticed "involved/intricate" operand "A" can cause issues with the cut especially then the B is relatively simple. ...I know it sounds stupid, but try exporting your model into .3ds open that and try your boolean compound again... I've solved a few boolean issues with this solution. (You can go back and save it in .max after your done if you wish)... You can also try using a higher poly-count operand "B" (like a 10 poly box -vs- 6) Sorry... trying like hell to help out here... Like I said I usually hand-cut my stuff.

Subtracting removes the faces... leaving you to have to rebuild them. Personally, I prefer to cut the polys by hand... not as messy as boolean (useless-vert creator) and far more precise. You might also try collapsing the edit stack of both objects before trying the boolean...

Well... could be a couple of things: 1.) The faces of the "cookie cutter" are flipped. The residue faces of your cut will be the same as their origins facing... So if your using say a box and you do your cut, the residue faces will appear to not be there. Try flipping your faces on your cutter, then cut. 2.) Make sure your A and B use the same material. I've had instances there dissimilar materials caused weird things like this to happen. 3.) Make sure your NOT subtracting... At the moment... that's all I can think of.

Hey IAP-Blackbird, Got your pics. Believe me... I tried the "full LCD" concept and just was not happy with the results. With the data I wanted to show, coupled with the size of the gages and their resolution... It just looked completely unreadable to me. I also tried the "no-HUD" floating HUD concept and because of the HUD symbology is projected... it just looked weird / 1-dimensional. I may go back and finish the "full LCD display" and include it as an alternate cockpit in the future... but for right now, I'm running with this one. Call me crazy... but I've grown fond of the existing one. Weird about the missles... I've not had any problem with any of the loadouts?

Sweet as all-get-up! I'm so glad there's folks like yourself around who have talent...

I dig it! All "I" would have to do is slap a man-face on there... I've had my taste of the "other side"... no thank-you. LOL!

Well... in a nutshell.... don't go faster than Mach 4. Sorry... I had to do it! LOL! Seriously... with the speed this bird can develop in short order, keeping it within manageable performance profile is paramount. Sure you can "go" Mach 4, but the slightest directional input puts you in red/black out... so it's only useful getting from point A to point B. (And running down an home-bound enemy...) I find it's sweet spot is between 400 -to- 500 knots. Superbly maneuverable and steady as a rock. While dogfighting, I like to chop-throttle, horse the nose around (while blacked out), throttle out of this to find myself with massive lead on the plane I'm chasing (Usually a 29 or 27) ... though sometime they reverse while I'm blacked out... and I'm chasing air... so it's not perfect.

Thanks for the Kudos! The Circular HUD idea was a conceptual thing... Figured most HUDs are rectangular... choose a shape that would stand-out/be different - modern. I do intend to do a Stealth Pilot. Not sure if it'll be with the final release or releasd separate/later... all depends on personal time I can commit to the project.

Tis the way she's done... your disregarded. LOL! Still needs a little temp delta adjustment... I was testing her in level flight... seems dive speeds in excees of Mach 4.0 make her go boom (Why anyone would want to go more than Mach 4 is beyond me) Still... thanks to everyone for the feedback! This kind of shared input make a "so-so" release into a winner IMHO!

Hmmm.... The flaming butt "should" be resolved in this itteration. If it's not PM me and we'll discuss...

Hey Shin_kazama, Answers in turn: 1.) I played with the movie-style panoramic layout out and found it: a.) cluttered and unreadable b.) could not implement the on-screen targeting (no HUD in the movie) and choose to create a stylistic / functional cockpit in its place. In a nutshell... "Function over form". 2.) I don't care how sexy Jessica Biel is.... Do you really want her fluttering her lashes at you when your lining up for a bomb run? 3.) More internal capacity is already in the works... However it will still be somewhat limited as the size of the weapons bays cause clipping issues with some of the larger stores... and I'm not about to go back and re-model them. 4.) Max speeds can be increased, however doing so makes general performance delta so high as to be insanely unrealistic. (And she leaps of the tarmac like a bullfrog with it's arse on fire)... 5.) "Tin man" / UCAV is a possibility... however once the Talon is officially out of the chute, I have a few other projects I've promised to complete before I can even begin to contemplate a UCAV. 6.) Pulse-engine (or my interpretation of it) will be included in the final release. 7.) Personally I'm not real fond of "Betty"... but I may add it in final release if I get enough requests for it. 8.) Sorry... HUD stays... It's a design concession I've made and I'm sticking to it. HMD would be really tough to model and I'm not the person to tackle it.

Hold tight... final package will have unique sounds.

About time someone with some honesty responded... ROFLMAO!

Yup... New version available! Was being sneeky about it to try and get some early feedback. Figured eventually the cat would get out of the bag... Newest version HERE putz with it and feel free to give feedback... Thanks!

... I don't even want to know what fuels the afterburners... Is it possible to break the wind...er... sound barrier"... while flying...er running at those speeds? :D

Me and my P.11c are like roaches... your never safe from us rearing our ugly heads.

CatsEyes... FWIW... My PZL P.11c, which I modified to run in FE works wonderfully.. If interested, grab it here: Zur-TECH.com

Right now I have a couple of FM gurus looking into FM... if that fails... I'm going to have to resort to begging TK to help me figure it out.

Issues: Right now it will catch fire and explode if you exceed 2.2 Mach. It "appears" to some how be a limitation within the game engine as one can hold a high AoA at high altitude with full burner forever and not explode... thus it's a "speed" issue and not a "heat" issue as I previously assumed. Capabilities: Presently is only configured for A2A and RG_A2G. No iron ordinance is loaded "yet". Extremely manuverable... to a point where you have to slow down to fight or your constantly be fighting red/black outs. Excellent dog-fighter and low alt CAS because of fantastic low-speed maneuverability. I'm presently working on finishing up on version 3.0 3.0 will include: -Updated high-level-of-detail model with 4 recursive LOD and a proper shadow LOD. -Updated / expanded weapon load-out. -updated HUD - Complete and functional cockpit. Stay tuned for more on this release...

"Fake" F/A-37 Talon is available at the above listed website... ...And hold onto your bloomers... there will be a v3 release coming "very soon". ;)

The Talon is presently "borrowing" the sound files of the F-14... You can either install the Tomcat or edit the sound file reference to one that already exists.