Jump to content

pvince

+PREMIER MEMBER
  • Content count

    23
  • Joined

  • Last visited

Community Reputation

12 Neutral

About pvince

Profile Information

  • Gender
    Male
  • Location
    VAL D'OISE FRANCE
  1. Mirage F1C_73 update is on its way for the release. We have slightly changed the French F1C mods versions split. This first variant is still the F1C as they were at the very beginning, when initially delivered to the French "Armée de l'Air". They had not yet the "BF" RWR and the Cyrano IV radar was the "early" version (scope and radar modes). Those aircraft were never retrofitted with BF, but the radar was, later, maybe progressively, upgraded to the new version (new scope, new modes). The mod is presented with the historical accurate numbers of the aircraft at their very first delivery in the squadrons: EC 2/30 30-Mx EC 3/30 30-Fx EC 1/5 5-Nx EC 2/5 5-Ox We have also added EC 1/12 12-Yx aircraft, but they were not from first delivery, they came from some of the squadrons above (themselves receiving the new F1C-200) and were reassigned to 1/12 quite early. The period covered by this mod is 1973 to 1981, so that we can have in the mod the initial external profile without BF, "early" squadrons decals, and "early" scope in the cockpit, all together. Another mod will present the same aircraft in the 1982 to 2003 period: "late" decals and new scope (F1C_82, to be released) The next 13 F1C that were delivered to "Armée de l'Air" had the BF RWR. After that they also had the refueling probe and those last ones were called F1C-200. The "F1C_RWR" mod (to be released) will present those aircraft (with BF but no AAR), for the full period (1975 to 2003). To be 100% accurate we should also split: early scope as initially delivered and later retrofit with upgraded Cyrano IV. We've not done it. Maybe a later introduction ! For now they are all in "upgraded" Cyrano version. The Mirage F1 team
  2. Thank you for the wonderful work. I have a question : the new release 2.0 now uses the "early" cockpit, with the "old" radar display. In previous releases, the "old radar" was on F1C_73 only (v1.3), F1C_81 (v1.2) was with new radar, and for me, therefore new display as well, same as F1C_80 (v1.3), only the RWR removed. Does it make sense ? Is it confirmed that the version without RWR, but new radar, had the old display (first F1-C retrofitted with new radar) ?
  3. Mirage F-1C_82

    The new release 2.0 now uses the "early" cockpit, with the "old" radar display. In previous release, the old radar was on F1C_73 only, F1C_81 was with new radar, and for me, therefore new display as well, same as F1C_80, only the RWR removed. Does it make sense ? Is it confirmed that the version without RWR, but new radar, had the old display ?
  4. It is not the vertical speed, I guess it is the airspeed when climbing, and it is in m/s.
  5. Just tested and I confirm ALT+W works (on ground and in-flight), but not ALT+G and ALT+J.
  6. For adjusting attachment position and angles in data.ini, for example, for external stations but also internal (interferences or weapons seen outside of the closed bay). Exactly LODviewer does already read data.ini (hitboxes, collisionpoints, component names and maybe other things I forget).
  7. Pilots and seats would be useful for positionning them and adjusting hitboxes. Following the same idea, also the weapons could be great. In a first step, only one weapon on only one station could be good enough. With one list to define the station, and another one to select the weapon.
  8. It's a "keep it all" campaign. Read the terms and conditions. "If your campaign uses the Keep It All (“KIA”) payment model, you always keep the money you raise. It doesn’t matter how much you raise or how long it takes."
  9. Hello. I have not found any info on this in previous topics and knowledge base. Is this statement in data.ini still valid in SF2 ? What is it for ? I tested with and without (A-10A_78 stock, gear) but did not see an obvious change.
  10. 0.62 fixed both, just checked, and limit texture resolution even not needed. That's great. Thanks.
  11. No the option does not help but yes they are 4k, however, in 0.52 the same with 4k textures is not slow (only loading is longer). Another remark from later use, version 0.6x is case sensitive for node names. If case is not exactly the same in the .LOD and in the data.ini, hitboxes and CollisionPoints will not show up when node is selected.
  12. Super Etendard is modified (HitBoxes + CollisionPoints) There are also some older updates I already had done: fuel tank capacity, tail hook deflection... Super_Etendard_Data.ini
  13. The new version (0.6x) is not compatible with ANSI code (version 0.52 has not the issue). It is probably the combination ANSI + some special characters in the file. Typical problems then: - data file not loaded - numbers.lst : numbers not shown in individual markings dropdown list (detected because of '°' in the text file) - textures.ini : texture not loaded (suspected character is 'é' in 'Aéronavale' ) And for your info, unfortunately still very slow for me also with 0.61. Sometimes it improves after some time after the model is loaded.
  14. I remember I read formerly somewhere in the forum that the gun must always be at 0° in the LOD (hidden in the fuselage then).
  15. And here is mine. My PC does not freeze, but execution is very slow, and with delays on controls. osg_logfile.txt
×

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..