swambast

Great, thanks again for all the positive feedback. Forgot one cool screenie though; shows how easy it is to add a new properly scaled target objects. Just right click anywhere on the grid, select a new macro from the menu, and choose from the pre-categorized list of populated WOV target objects! If you look closely at the screenshot, you can see how we have all the objects nicely already categorized for you (i.e., Airfield Objects, Harbor and Naval, Vehicles, etc.). The other cool thing is if you just click a macro object, you can quickly get a graphical thumbnail picture of the macro, too. I think you will find that after a while of using the tool, it becomes so easy to manipulate objects and create the respective target area .ini, that you start craving more objects! So, if anyone has more objects they would like added to our library, please feel free to PM me and I can provide you more details. Enjoy all, thanks again for your support!

All, I'm working on some program updates that I think will be beneficial to the entire community - the focus is on the Target_Types.INI file. I am trying to capture all known variables that a target object might contain - so far I have the following (sorry, it's just a straight programming data dump). Are there ANY other values / fields that I might be missing that should be included? Thanks in advance for your help - I think the output of this development tool will be very helpful to anyone who ever had to manually add objects to their Types.INI files (isn't that just about every modder here... :yes:) .ColumnHeaders.Add , , "TargetType" '0 .ColumnHeaders.Add , , "Name", 3000 '1 .ColumnHeaders.Add , , "Full Name ", 2000 '2 .ColumnHeaders.Add , , "ModelName" '3 .ColumnHeaders.Add , , "TargetType" '4 .ColumnHeaders.Add , , "ActiveYear" '5 .ColumnHeaders.Add , , "TargetValue" '6 .ColumnHeaders.Add , , "UseGroundObject" '7 .ColumnHeaders.Add , , "DamagePoint" '8 .ColumnHeaders.Add , , "ArmorValue" '9 .ColumnHeaders.Add , , "ArmorType" '10 .ColumnHeaders.Add , , "RepairRate" '11 .ColumnHeaders.Add , , "StartDetectChance" '12 .ColumnHeaders.Add , , "StartIdentifiedChance" '13 .ColumnHeaders.Add , , "IncreaseDetectChanceKey" '14 .ColumnHeaders.Add , , "MaxVisibleDist" ' 15 .ColumnHeaders.Add , , "DamagedModel" '16 .ColumnHeaders.Add , , "DestroyedEffect " '17 .ColumnHeaders.Add , , "DestroyedModel " '18 .ColumnHeaders.Add , , "SecondaryChance " '19 .ColumnHeaders.Add , , "SecondaryEffect " '20 .ColumnHeaders.Add , , "CollisionMesh " '21 .ColumnHeaders.Add , , "ZBufferOffset " '22 .ColumnHeaders.Add , , "FlatObject" '23

Thanks Wrench - sorry, I think I should have clarified! Just wondering if there were any actual variables that could be used that I may have missed (entries in addition to the things like "MaxVisibleDist" , "DamagedModel", "DestroyedEffect", etc.). But hey, the explanations are appreciated too, thanks. If anyone else has more to add, please pipe in.

All, thanks for your continued interest and patience. A special note goes out to all of you who were recently added and recommended for the Beta Team - please Stand-By! The next Beta release of the program will be by far the largest, most comprehensive release to date. Tannethal's been working overtime to deliver extra object treats supporting STT. The 1.5 beta release is taking much, much longer than expected, but I believe it will be worth the wait. Major updates will include: * now over 200 fully supported target objects complete with proper scaling and .ini entries - covers all of the stock objects, the Factory Place, Polak's Object Library Set and CA_Stary's hangars with special thanks and appreciation going foremost to Tannethal and Polak - and Wrench and CA_Stary * Backward compatibility with previous/custom FSSC files - STT will now convert previous FSSC files into the custom STT format allowing you to save your original file and leverage the power of STT compatibility going forward * Ability to parse out and work on any single .INI section from within any Targets.INI file (greatly accelerating time saved especially if you like to work on one area at a time) * Greatly enhanced translation and conversion error-checking: will detect missing objects from your Types.ini file and highlight them within STT line by line to show you exactly what's missing and where, enhanced output/error logs, and perhaps the greatest feature still is TITS - Target Intelligent Translator Syntax. TITS will automatically resolve errors/missing object entries written out by FSSC - a major break-through for those that have ever used FSSC and were stuck renaming and fixing hundreds of faulty Macro# entries! All those headaches and wasted time are no more - STT will dynamically fix many of these automagically during the conversion process including missing coordinates, missing file names, broken rotations, etc. * Advanced Array Loading Code from FSSC to .INI - now loads approximately 100 target objects in 2-3 seconds (increased speed of about 20% over previous versions) * Completely revised user interface with enhanced single-click file viewing and directory navigation for quick access to the files you need to reference most * Support for the ActiveYear target objects variable added * Unofficial support for the October 2008 Patch update (testing still in process) * Quick Start Guide Tutorial: complete with graphics and step-by-step getting started guide * FSSC Support using Background images will now properly convert with STT into Thirdwire .INIs (see the awesome example below!) * And a lot of other minor fixes, tweaks and enhancements... Some screenies: Main Screen Tannethal's "tests"

Guys, just a comment here. The YAP2 developers definitely got the flak effects right! I don't have any insight into exactly what they did, but for the purchase price alone it more than provides at least for me the "flak immersion factor." When the flak guns start opening up on me, I literally have a sense of panic as I can watch them getting closer and closer especially if I do not perform evasive maneuvers. It just feels realistic, I have been downed by "YAP FLAK" often enough to put a habit into making "evasive tactics" part of every target run - and I think that is exactly what they set out to accomplish. Obviously you need to balance your investigation time vs. the YAP2 cost, but just another option to think about.

Check PM...thanks.

HOLY COW MISOFTCIA, THAT IS BEAUTIFUL - KEEP UP THE GREAT WORK, WOW!!!

Storm...a revisit to this old thread just may help...steady (but slow) development and outstanding support by one dedicated beta tester...this option might just be the answer you're looking for!: http://forum.combatace.com/index.php?showt...=34895&st=0 PM me if interested. Even though it's still in beta, I think you might find the amount of time and effort you save amazing, and just maybe you might really come to like it.

Sounds great, where do I download?

I really do love the new YAP2 especially the awesome jungle trees/foliage, but Brain32's tile rework is still the masterpiece that I prefer regarding terrain tiles... Can anyone please provide some insight into how I may be able to get this to work within YAP2? Thought it would be easy just copy/paste of the tile sets, but obviously I must be overlooking something, because I'm losing the YAP2 trees/foliage, thanks for any insight!

Thanks Kevin, I actually just kept the YAP2 Data.INI as is - didn't change anything there. Then did a copy/paste of Brain's file sets over, keeping of course the original YAP2 Data.INI - thought that should have worked...

All, I am the proud Daddy of 2 young boys ages 6 and 4. They watch in amazement as we do sight-seeing missions and fly around in WOV, and love being my "co-pilot" helping out with the gear, flaps, etc. They always want to look at the outside of the plane of course, and like me too zoom in so they often comment "There's me and you, Dad." I love it. I was wondering if someone would be so kind as to consider making some custom "pilot faces" from actual photos for me, so I can literally put their faces in the cockpit (and unfortunately, my ugly mug too). Was even thinking about throwing in the wife's pic too. I would need four custom pilot faces (me, wife, two boys) - ideally each with a helmet on / helmet off selection. I understand your time is valuable, and would be willing to pay a small fee in return for your work. If you are interested, please just send me a PM - thanks for your consideration! Steve

That is FANTASTIC work...great stuff! I will round up the pics and send you an update via PM...thanks so much!

Alex, really!!!??? That would be so awesome of you! Wow - how cool. Let me know what you need, I would be happy to test anything out for you, thanks so much!

Here you go: http://www.yankeeairpirate.net/buyyap.html Don't forget John and Team did pledge their loyalty to existing customers...hopefully the discount coupon will be available soon, and no, I'm not kidding.

For custom objects added into the Target_Types.ini files, how does one make it so they are not assigned as a potential target. Example, I've created and added a basic aircrate into the _TYPES.INI file and it displays just fine, but does that mean that an "Aircrate" could potentially be assigned a target - I would assume so...? Thanks for the clarification! Maybe I'm getting confused on where the .lods go - objects, terrain, etc...?

You're the man Kevin, that's great info - thanks! Which one of your remakes do you think would be best to learn more from and leverage object .lods best for populating an airbase? Where would I find Polak's Object Library - I must have missed that!

Basic question - how come sometimes certain .LODs will only appear in missions and can't be used as target objects in a location (i.e., an airbase). If I update them in the _TYPES.INI and properly reference these, shouldn't they in most cases show up as target objects too? I can get 95% of the .LODs that I want to appear, but every once in a while some of them just don't show up no matter how much I double-check and move things around. I understand the fundamentals of UseGroundObject=TRUE/FALSE and placing the .LODs, etc. in the Terrain folder, etc. but I must be missing something else. Thanks for any additional insight!

Irfanview will open this for you: http://www.irfanview.com/

New beta release will be available within 2 weeks: a small group of special invites went out already. Thanks to those who have responded and are joining our Beta Team! :yes: Although I wish to keep the team small and focused on those with previous experience (FSSC prior experience is a huge plus), we're going to take a few volunteer requests as well. So if you're interested, just PM me and let me know if you have the time to actively participate over the next month, what your FSSC experience is, and tell me how much you can help make the WOV world a greater place by beta testing STT... -Swams

Hey, thanks all for the feedback, much appreciated! To answer a few questions posted here and there: 1) Yes, I consider CombatAce my "home turf." That means for the community here, I will extend a special invitation to a very small select group of individuals and ask them if they would like to join the STT Beta Team. Obviously, I am going to take preference to those with the most experience; those modders who have already poured their soul into doing it the hard way, and those who also have the potential to return the most value back to the community. 2) Wings Over Vietnam with SPv08.30.06 is the only officially supported Thirdwire title that STT supports at this time. 3) I don't own any of the other Thirdwire titles except for First Eagles which I haven't played in a loooong time, but as eraser_tr mentioned, I believe the program could quickly be adapted to other titles. 4) I am unsure exactly what changes have been made in the latest patch to WOV, I would have to examine the _TYPES.INI, _TARGETS.INI, and assess whether any folder structures have changed. If it is OK to distribute these files since I already own the game, then please send to me. Otherwise, I will examine these at a later date. 5) Yes, the program examines all objects that are created within FSSC against Thirdwire's _TYPES.INI file. It's so simple, just put a check in the box and run a quick test. So, if you are using FSSC and you add a "Sampan" object, and "Sampan" does not exist in your VIETNAMSEA_TYPES.INI, the program will tell you there is an error, highlight the exact row in red, and present you with a summarized output log, like the screenshot below shows. I give absolute full credit, thanks and acknowledgement to "Tannethal" for this. He was the one who originally "challenged" me with the concept. Out of respect for his past work on the airbases and his heavy use of "non-stock" objects, I feel like this is my small personal tribute to him! 6) Guys, yes I take requests to help improve the program. For those already asking about whether I accept donations, I could not be more grateful. I would say hold off on the donations to me for right now - I would ask that you send them to Dave "Wrench" in support of this great CombatAce community. What I need now is just encouragement and more creative ideas to make the program incredibly useful, user-friendly and valuable - maybe later I'll ask for the donations. I want this to save you time and effort, and allow us to populate scenery with (target) objects as quickly as possible. You modders are miles above me in terms of skills and you know the pains you continually have to go through each time, so let me know what else I might be able to do to help in return. 7) No, at this time it is against my licensing agreement to use the program for any commercial purposes whatsovever. 8) Someone asked what they might be able to offer in return: here's what would interest me greatly: if anyone has ever made "junk" airfield objects, things like: big stacks of plane cargo, pallets/crates/boxes, airfield mechanics, airfield ground crew, US Jeep with an actual driver, groups of U.S. Soldiers and Vietcong in varying sizes/formations, etc. so that "we could place these around the airfields to make them come alive?" And yes, I already am a proud owner of Yankee Air Pirate (YAP), but of course using those objects in conjunction with my program would not allow for a public release and would be illegal - please don't ever do this. Regards, Swambast

Congratulations to all - this is absolutely outstanding! Thanks a million!!!

Swambast Target Translator ("STT") DEMOS: For some reason, the demo is all funked up when using Firefox (my personal preference) - so please use Internet Explorer to view! Click the link to view: Demo Part 3 - Converting an FSSC .SCN file back into a Thirdwire Targets.INI file Enjoy! Swambast

All, I have been working relentlessly to bring this to a reality, and have made significant progress. As promised, here are some quick demos of the beta in action. All of the coding for the beta is complete, and in the classic "2 weeks" or so, I may be looking for additional beta testers. Enjoy the demos, hope you find it exciting and full of potential! Swambast Target Translator ("STT"): For some reason, the demo is all funked up when using Firefox (my personal preference) - so please use Internet Explorer to view! DEMO Intros (just click the link to view!) Demo Part 1 - Converting an .INI file to an FSSC .SCN file Demo Part 2 - Manipulating and adding Target Objects within FSSC Enjoy! Swambast

Easy racin...try these links as these may help you out more...! http://forum.combatace.com/index.php?autoc...p;showfile=1494 http://forum.combatace.com/index.php?autoc...p;showfile=7830