Any news ??? (ODS OF fixes by Fafa)

[Couby]

The project goes on and my site remains opened.

I was very angry yesterday, some attitudes make me sick. I won't let credit to people who make personnal wars, personnal falcon version wars or keep recurrent or definitivaly work which could be optimised and used for the community. My goal is to share and use as the better as possible every work, so no offense... I don't want this community to be affected because of some individuals. So I won't stop now.

Sounds good .

Bon courage et bonne chance pour la suite .

[Fafa]

Merci, je vais essayer de faire quelque chose de potable.

[RingoSurf]

Sorry for my question
...but ODS v0.7 will be compatible with falcon4 allied force?

[Snake Man]

Couby and Fafa, this is english forum.

ODS v0.7 will be compatible with falcon4 allied force?

Yes very much so, more than the v0.6 in fact as now we have fixed the broken installer. Don't worry, you'll have good time in AF using ODS v0.7 release.

[derStef]

Nice List of ACs fafa! would be very great to have them all in database.

but what do you think about my whishlist for RV theaters in general, because they can be use in a great variety of theathers!

Models/Skins which would be very nice & useful for different Theaters&Campaigns in RV!:


Models: important ones:
A-37 Dragonfly (for Vietnam theater)
J-35 Draken (for Europe theater)
F-5B/F Tiger (general)
F-15B/D Eagle (general)
F-16s (Blk.60;ohter dorsal spine models)
F-104 Starfighter (general)
Bae Hawk (general)
F-CK-1A/B/C (Taiwan theater
EF-18G Growler (general)
KA-6 CARRIER Tanker
Alpha Jet (general)
Sea Harrier (general)
F-2 (Japanese F-16 derivate) (general)
F-1 (Japanese Fighter)
Mirage V (Fighterbomber for Europe theater)
O-2 (general)
V-Bombers (Vulcan, Victor, Valliant)
P-3 Orion (general)
B-47 Stratojet (general)
B-58 Hustler (general)
J-22 Orao (Balkan theater)
Lightning (Europe theater)
Jaguar A (general)
B-66 Destroyer (general)
T-50 Golden Eagle (Korea theater)
B-57 Canberra (general)
Yak-36MP (VTOL)

Skins:
RoCAF(Taiwanese) F-16 & F-5
Japanese F-15J
Egypt F-4E
Iran F-4D/E, F-5E, F-14
Turkey F-16, F-4E
NorthVietnam MiGs
Agressor F-15, F-5E




how to get these working, they are already in RV database, but not really working.
as i added them whith they Squardron is not shown up in Camaign menu minimap in RV, but some of them are flyable in TE's) what is the problem with these models below?????

F-5A
S-3
F-16 Agressor
B-52D/G
AC-130U (incorrect model => F-18)

----------------------------------------

[ccc]

how to get these working, they are already in RV database, but not really working.
as i added them whith they Squardron is not shown up in Camaign menu minimap in RV, but some of them are flyable in TE's) what is the problem with these models below?????

This is the key question for those want adding more new vehicles to database.

sorry i have no idea about it - Jim is the one in the know.

[derStef]

how to get these working, they are already in RV database, but not really working.
as i added them whith they Squardron is not shown up in Camaign menu minimap in RV, but some of them are flyable in TE's) what is the problem with these models below?????

This is the key question for those want adding more new vehicles to database.

sorry i have no idea about it - Jim is the one in the know.

ah OK! thanks CCC


is JimG meant???? is he still around i forums

[RingoSurf]

RingoSurf wrote:
ODS v0.7 will be compatible with falcon4 allied force?

Yes very much so, more than the v0.6 in fact as now we have fixed the broken installer. Don't worry, you'll have good time in AF using ODS v0.7 release.

that good news !
personaly I think that ODS (midle east) is the most important scenario for falcon and you are doing a great job
cheerio..

[Fafa]

...

[Fafa]

Problem here, need a 3d/lodeditor help... Switchs and dofs not correct after importing them in OF DB. Please help... thanks in advance.

No wheels for c130H
Bad wheels position on the rear gear for the LAVI

Dunno how to correct this.

[ccc]

lavi, you have to use correct fm.dat.

[Fafa]

Ok problem solved, I get the good dofs and switch values before and the simdata was also good but... seems that the sim folder on the root takes the advantage on other specific simdatas in other folders.

what is the syntax in the Theater.TDF file for pointing to the good place ?

simdir ?
simdatadir ?
zipsdir ?

The problem is that i'm working on an of 4.5 version and there will be updates in future so new aircraft.dat so If I only add lines to this folder they won't be active in the next OF Update. I need a separate simdata.

[Couby]

As far as I know Fafa, this command has been implemented for RedViper, not in the exe used by OpenFalcon.

With OpenFalcon either you use only one simdata, or you have to build a theater switcher in order to switch sim folders (what would make the use of this external theater switcher mandatory).

Another command, used in OF tdf files this one, is bugged. This is the moviedir command.

[Fafa]

Ok so I'll have to update the simdata each time there is a new release for OF...

[Couby]

When I was working on ITO2 conversion for OF, I made a deal with Naldo, in order to build a coordination between theater developpement and OF upgrades.

After the 4.5 release GlobalFalcon had to stop any DB and 3DDB updates. This part of the modding being assigned to the DB/3DDB department of an OF unified mod team. As the only way to do for OF boys, is to manage a unique DB .
What implies coordination.

There's no OF mod team, and I don't know what this project is becoming. It seems to be dead before to be born.

I recently discussed with Naldo, asking him to comply the PMC naming structure for theater add-on, for the Balkans.
No way to convince him. If I understood well he considers that in reality, there are so few modders, that it is useless complying such standards. By extension I understand that as it is also useless to build any coordination.

In other words, make your work on the DB/3DDB, and release it with a big propaganda operation in order to win final users support.
You need to have done a very interesting work on that one so that for final users it is worth choosing it. It would then imposed by itself...

Or you ask Naldo to be in charge of the OF DB/3DDB. That may be the best solution but implies a lot of work.

Good luck .

[Fafa]

Ok thanks COUBY.

[Snake Man]

I recently discussed with Naldo, asking him to comply the PMC naming structure for theater add-on, for the Balkans.
No way to convince him. If I understood well he considers that in reality, there are so few modders, that it is useless complying such standards. By extension I understand that as it is also useless to build any coordination.

Hehe... I guess we can rule out the OF database support for theaters then too

[Fafa]

Skins and lods added since my last fix...

Aircraft ------------Sets-------- Orig OF NAME-------- ADDED

F16A-IAF 10 F16C-AGRS SIMDATA
F16A-JORDANIA 1 F16A
F16B-IAF 1 F16B
F16C-EAF 1 F16C-40
F16C-IAF 1 F16C-30
F16D-IAF 1 F16C-52+ LOD
F16I-IAF 1 F16C-52+CFT LOD
A4H-IAF 4 A4M
AN2-IRAF 1 AN2
IL28-H5-EAF 1 IL28
AV8B 2 AV8B SIMDATA LOD
MIG23-SYRIA 1 MIG23 SIMDATA LOD
MIG23-IRAF 2 MIG27
SU27-ERITREA 1 SU27
SU27-ANGOLA 1 SU27
SU30-INDIA 1 SU30MKK
MIG29A-IRAF 1 MIG29A
MIG29OVT-RUSSIA 2 MIG29S
MIG29K-RUSSIA 1 MIG29G
C130H-IAF 1 C130H SIMDATA LOD
SU33-RUSSIA 1 SU33 SIMDATA LOD
SU35-RUSSIA 1 SU35 SIMDATA LOD
LAVI-IAF 1 F16-25 SIMDATA LOD
F15C-IAF 3 F15J SIMDATA LOD
F15I-IAF 4 F15DJ SIMDATA LOD
TU16-IRAF 1 TU16 SIMDATA LOD
TU16N-IRAF 1 TU16 SIMDATA LOD
TU22-IRAF 4 TU22 SIMDATA LOD
A50-IRAF 1 A50
AN24-IRAF 1 AN24 SIMFATA LOD

For the moment....

[Snake Man]

A dumb question... these OF skins youre gathering, do they work 1:1 the same in RV too?

I was thinking that when we make the new installer, we just use these skins for OF + RV and leave the AF guys hang out to dry (as they cant use .dds skins)?

[RingoSurf]

Snake man said:

I was thinking that when we make the new installer, we just use these skins for OF + RV and leave the AF guys hang out to dry (as they cant use .dds skins)?

I reccomend don't forsake us in need !

[Fafa]

A dumb question... these OF skins youre gathering, do they work 1:1 the same in RV too?
I was thinking that when we make the new installer, we just use these skins for OF + RV and leave the AF guys hang out to dry (as they cant use .dds skins)?

No, the DB is too much different, but the aircrafts I'm adding are extracted from different versions and in particular FF3. I didn't remaped too much textures at the moment so I think it won't take too much time to make a specific RV version. By the way some of the lod I changed in this version are directly extracted from FF3. Because with RV we can't access directly to the lod data via LE6.10 this work will be only based on changing skins and renaming the aircrafts entry. The new structure of RV can't permit compromise and I suppose the tools useful for it are seriously kept.

For AF the big problem is the not used DDS so even with a tool to convert DDS to BMP 128 or 256 ( bigger is possible ?) and integrate it, it is possible but it would be very very very long

[Snake Man]

Fafa, whats the status on your OF edits?

Also please take a look at PMC Editing Wiki: User Interface and let me know all the latest goodies for OF section?

[Fafa]

Work in progress

Have to replace other lods/adding aircrafts and adapt hardpoints and fm's... Then have to finish my F14 IRIAF skin and change 2flags in the UI. Then tacedit the new campaigns.

ETA 2 to 3 weeks in the best conditions.

PS :The interest of this new DB should be to make an ITO2 DB (3/4 of aircrafts) for OF. Campaigns should have to be made.

PS2 : I suppose with the ITO2 conversion for RV, an ODS Conversion for RV should be possible with only adding some of the skins of my project. Only the tacedition of the campaigns should have to be made.

In conclusion, I think ITO2 and ODS DB's should not be as much as different as it seems.. For AF ? mhhh quite different because of DDS.

[Fafa]

I'm looking for closter the creator of -> viewtopic.php?p=171264#171264

anyone has seen him ?

[ranger822]

Derstef wrote about items in DB but not working. I have encountered this many times in my own work and in most cases the DB is probably incomplete in some way for the a/c or item. This does prompt me to make a post here for the benefit of those interested in not wasting their time.

There is a reason for the incomplete nature of DB's. DB development is on-going and some items were added for the purpose of future development - so just because something was loaded into the DB doesn't mean it was intended to work. As an example, ITO2 has stuff in it for Falklands, Taiwan, and EMF in "ANTICPATION" of future work. But, it isn't ready - it is in the background waiting for future development. I suspect other folks playing with DB stuff have done similar things.

The other thing is it might be more useful of ones time to consider what final product is desired. You don't need everything in a database to run a given theater - - working thru an Order of Battle you probably require just a portion of the database to create a very nice campaign. All the other stuff is just "STUFF." I think we get so excite about what is in the database and getting it perfect that we don't question "WHY" we should care or spend so much time on it. Once you get down the path of DB work you can quickly feel yourself sinking further in without any hope of completion. Someone always wants to add "just one more thingy." Falcon will never be done, the executable will always need updates, and in many cases the job will last longer than most development teams interest.

Start with a simple, realistic, obtainable project. Decide on a few specific aircraft that you really want to develop to perfection, forsake the rest. Then with plan in hand go build your terrain (if not done already), make a simple working campaign using simple models/placeholders - then go back and spend time on tailoring the DB to your specific needs.

When you fly - all those other aircraft in the DB invisble (and a distraction to most development) - most of that stuff you will never even see except for a fleeting moment in dogfights. Why fret over all that stuff? IMHO if you fly (not develop) you probably want a nice view from your cockpit - so great 2d and 3d cockpits, detailed airbases to fly in/out/and bomb, and great terrain to pass the time in transit. Forget about the A-37 Dragonfly! There are much bigger fish to fry.

[Snake Man]

Have to replace other lods/adding aircrafts and adapt hardpoints and fm's...

Can you tell me how to edit flight models?

ETA 2 to 3 weeks in the best conditions.

Ah, I was thinking of more like 2-3 days

No worries, there is plenty of theaters to go around first, lets say I'll pick Taiwan and edit it for now and you continue editing the ODS OF side, if there is some changes need to be made in my part, I'll do them.

Btw for an update, I already posted the fixes I now made into the v0.6 bugs topic, but to add for that... I've now pretty much fine toned the NSIS Installer for supporting AF/OF/RV user interfaces and databases.

So ODS is looking good for v0.7

[ranger822]

Thanks Couby . . . that is a relief. The good news is I found some broken/bad links and updated them - so everything is back up in place for Cobra-ITO

[ranger822]

SM - what specifically do you want to know how to edit? I can give you some basics that I have learned. Haven't really messed with the performance tables and I don't have a definitive list of all the codes/numbers for the supplemental data at the end of each FM. What might be useful is to create an FM or placeholder that has commented sections for all the FM datapoints explaining the significance of the item and what values different executables can apply. Sounds like a great Wiki item when I get aroudn to it.

[Snake Man]

Well wiki was my main point, I want to add the stuff into wiki and at the same time naturally learn (or skim through the text anyways) it myself. We have all these aircrafts but who knows what kind of microprose 1998 default copy paste flight models in them.

[ranger822]

It should go without saying that all FMs ought to have a very detailed comment section at the beginning that provides info on the version, default settings, what exe specific model, exe, etc. Some of this is done but I think many the model is copied and slight modifications made but the mod - and other info isn't specifcially stated - now we have FMs of unknown origin and it is now more difficult to figure out what the model is doing versus what it should be doing.

[Fafa]

Hardpoints problems here I don't know how to resolve...

[Fafa]

Ok, I'm working on it for 3 days and didn't find the solution again. The project is on stand by still there is a solution. 2 reasons for this :
1/ All the integrated ITO2 AC meet the same HP problem. I have not finished to integrate the others. So the problem will be the same.
2/ I tried to permute lods, rack.dats, I tried to put other rackgroup references in simdata, tried to modified hardpoint edits with F4BROWSE and nothing was changed.

If someone could help and explain to me the reason why ? thanks.

Thanks also to people who give me advices.

Fafa.

[lamurt]

hello Fafa et all,

any ideas why the host is usually hanging at the 5th pie during multiplayer while the clients can enter into the pit?
this hanging is not a ctd mind you, if patient enough host can see the cockpit after 3-4 or more minutes, but it's not very practical.

also can something be done with the installation, it takes 1.5 hours ffs!.. if it's for lpaf, well to hell with it.
scoob's v0.512 mod for OF is very a nice drop in mod, extract it, edit the .lst and voila you have your ods ready...

[Closter]

@Fafa:

Sorry, I havent seen

I'm looking for closter the creator of -> viewtopic.php?p=171264#171264

anyone has seen him ?

I will send you his (Darkcon's) email address via pm. He's not fluent in english, try to simplify.

[Jaguar]

hello Fafa et all,

any ideas why the host is usually hanging at the 5th pie during multiplayer while the clients can enter into the pit?
this hanging is not a ctd mind you, if patient enough host can see the cockpit after 3-4 or more minutes, but it's not very practical.

also can something be done with the installation, it takes 1.5 hours ffs!.. if it's for lpaf, well to hell with it.
scoob's v0.512 mod for OF is very a nice drop in mod, extract it, edit the .lst and voila you have your ods ready...

Yeah we have the same problem with ODS v0.6 in MP TEs... Lot of participian hangs on pie5....

[ranger822]

Fafa,

seeing the pic tells me you should have a discrepancy between your FM and vehicle data record. I think you know this. I sincerely think the problem is a different FM for the model than the one needed is being applied.

Why not try this:

1. add a new flight model to your acdata.lst in your simdata.zip
2. add a new ACD to your database and reroute your vehicle record to a totally new ACD, alternatively, find an ACD record that is currently not being used by any aircraft (there should be several).
3. I will send you an FM to work with the Mirage IIIC-YKW-73 for testing, just add to your Simdata.zip folder and note the name for your acdata.lst file update.
4. I can provide you a screen capture of what you should see in the hardpoints data in the Mirage IIIC-YKW-73 vehicle data record. Make sure your entry is the same.
5. Compare your rack.dat file with mine - are they the same? If so then the should tell you not to make edits to the racks - rather the edits need to be in the vehicle record, ACD record, and simdata.zip

Will send you the stuff tonight - let me know the results. If it works then you know the solution. The next thing to do is create a simple Cobra-ITO install for archive purposes - you can then open it up and extract all the files you need or data records you need.

[Fafa]

Thanks again Ranger
I try this as soon as possible.


F15 PROBLEM :



This is I think the response of my problem. All the HP are in the same place on the F15'S FF wings and OF makes them on on one on one. So my question is what is the manoeuver to move those Hardpoints ?
( Moving HP in parent section changes nothing).
I saw that F15E in OF has 11 HP vs 9 for FF model.

[ranger822]

Fabrice,

show me the pic for your parent record - how many slots in the header?
show me the slots in the parent record - what are there numbers? Did you update those slots and update the parent record when you appended the model and then opened up. You have to open the model and then cycle thru each slot node and update its slot values. Then when you return back to the parent record make sure you "update" close and reopen LOD Editor. Now reopen your parent record - are the correct slot values now showing up?

Open the model in LOD Editor - verify the slot number has the slot values for x,y,z. I can't imagine OF not using an LOD model like every other exe. Click your slot view -- if you have only three slots then your model must have your slots with only three values, that is why they are overlayed on each other -- the slots will appear where the model instructs them to go. - check all three views just to be sure.

You should also check the rack.dat file - if the file is the same for FF and OF then there shouldn't be any issues there. Otherwise - it is a whole new ball game - because the rack groups are set to pull specific rack models and textures - if OF is using something different that will complicate things a little bit. - - ARE YOU SURE YOU WANT TO STICK WITH OF? - -heheh just kidding

[Fafa]

Ok Tony, Swith gave me some ideas I have to apply. I'll try it tonight if I have much time.

Now you got an idea of my problem here ->




I'll send you as soon as possible of the references. Maybe ther best for me should be to send you all the files. I'll contact you.

[ranger822]

I sent you info on my Mirage IIIC-73 - lets focus on that one a/c - once we have it figured out and working the rest of the a/c should be trivial.