A.S

PS: we do really need a way to disable automatic record eachtime (imagine redflag or vFAT everyone on record...nahh nahh)

It happend, that 4 times, right at a moment, where i shot at a jamming target my "sim" crashed. Case description: F-15, Launch button (keyboard = ENTER), Saitek x52pro profile (pinky switch + trigger detend 2 HOLD) Here the .crash log: # -------------- 20100329-202334 -------------- H:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\UserInterface.dll # C0000005 ACCESS_VIOLATION at 021A8AB9 01:00037AB9 # # EAX = 00000000 # EBX = 00000008 # ECX = 00000000 # EDX = 43A26108 # ESI = 415CB0E0 # EDI = FFFFFFFF # CS:EIP = 001B:021A8AB9 # SS:ESP = 0023:0012FB10 EBP = 00000000 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00210246 021A8AB9 00000000 0001:00037AB9 H:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\UserInterface.dll ?changeSelectedItem@MultiColumnListBox@@QAEXHHH@Z()+79 PS: i would really love to know, HOW i can disable that automated .trk recording each flight to save some resources on my PC. Anybody plz? :huh:

sup Bearitall.....PS << :doh: ...no worries, my stuff is smokin to get 2.0 implemented in TCL, but needs few fixes (patch) ..right now=!=!=??°? ..omg no way :cry: (further details in TCL pm)

have you tried client = { history_size = X,

LOL ..interesting

HOW :helpsmilie::music_whistling:

2 different pairs of shoes here........ seems << does also not apply....numbers dont lie

If someone knows, i need to know the thrust values under full AB for F-15 Su-27 Su-33 Mig-29 (all variants) in numbers. (missing in tacref) Reason why is, a test setup (BFM) / thrust-weight-ratio equality + burning-time of fuel (< that i find out myself) (for all doggers out there....the 40%-52% rules dont apply anymore, even though i wasnt a big fan of it anyways)

Just a quick dogfight with Fusion (lets test this stuff here cmon) ...and a "hold on a sec..this is waaay off" :D

If you have enough RAMs, increase them. Doing so, you avoid them being relaoded too frequently in a precache radius (LOD radius). The Modellod range tweak has nothing to do with "loading them" or stutters, just how your cpu deals with them. It makes really no sense to calculate details beyond any visual range. Regards common files i would suggest a common modellod.txt file (available on forums of specific squads) rather then just sticking with the standart file. This way integrity can still be provided. PS: so far the game isnt bad at all in certain areas (nice work and honor to those who deserve it) but there are also certain epic-fail errors which particular ( flaps drag values and their "inverted F22" effects )* have been reported to devs...further tests in progress. *Test Flaps: engines off, constant descending at 150kts with slight negative pitch (gliding) applying flaps ....observing drag and speed loss = almost none sustain turns at 250kts at 4.5Gs ....applying flaps.... what happens is this: you gain speed !!! the current flaps "do lift" and also decrease AoA (drag) under load, but due to lack of enough surface drag values of the flaps surfaces, you speed up and can sustain with flaps more Gs and you GAIN speed in a way which should not be the case. Right now F = F22 button. Probably just an small error (just wrong value) but dramatic impact . Needs a fix asap! Best would be (as by many beta testers what i know wished) that you can NOT deploy flaps at such high speeds anyway (see AFM su-25T << there they thought about this) ...would be good to use them in combination with gears only...(smart workaround in logic sense)

as far for your stuttering.... change your precaching values

setting up right affinity mask in autoexec.cfg boosted my sytem up verz nicelz....*just experimented around

I remember you saying this long time ago, just yesterday i told fusion that you mentioned that once ..but why?

or copying the 27 into 15 and loosing weapons release like i did and causing other wierd "no response" results ingame online. :D

the sudden stop of joystick inputs have been reported now in several cases. except axes..they still do work. suprisingly running in on not-fullscreen seems to fix it for the most times ergo: effect>result>reason

thx..used that to adjust my "straight-line eyelook" X [13] vangles=0

.... HOLD Trigger to release missiles :D

oh thx.....btw same ole file and explosion stutterings ..(to disable them ExplosionExpoTime = 0) "i feel like reworking 4 years of community improvements once again"

Would also love to learn this...dont like setting up my FOV each time again and again ...(PS: i only use tir yaw n pitch with FIX FOX, what i fell natural and best for my config - widescreen) PS: how can i turn off head-tilting forever and from the scratch (shift F1) ? (Fancy cool feature, but ......meh)

2.0 seems to do alot things via lua, meaning, we know there are no new pyhsic engines or flightmodels, but yet lua "manages" to interact and give you the impression that your controls are different. (see x52lua etc) ....basically it works like an "overlay" additional controler. Now, how much bandwith takes that (usb - mobo ) and i noticed conflicts with saitek profiles (your profiler stops responding, buttons dont work suddenly...in few cases as noticed by some.) Anyone noticed that too? If that is true, that would mean to assign keys ingame rather then using keyboardemulations=?

put 40-50 ground units on the ground . fly away till you think, you shouldnt see them in detail anymore (like 4-6km) ...use 5000m as value...close to them and watch your obj fps counter ...then do same with standart settings.

edit: here we go

It is ok. That point is a legit point. I m quesitoning that myself long ago becuase i have to find a common baseline for TCL rules also...

Fair enough for 1GB ram and single core after the tweaks :D

Good point, but without i fear you will fail enjoying redflag-big scenarios. So we have to find a way what is allowed (legal) and what definitly can not be considered to be changed. As far as i hear, this can be done in the integrity checking system.