Tracker

Perhaps your MOD could change the lables on the CHAFF and FLARE counters so they would be correct...:D Now all we have to do is figure out how to get the settings to stick regardless of the server settings. :P

The prob with the Wiki is that we have a few loose nuts running around that would think its funny to send new programmers down the garden path of chasing a wild goose. A Wiki in which the Solid facts could be Locked down however seems rather cool however. and for you 'The GURU in the Sky' (zaGURUinzasky) http://www.wikipedia.org add that to your GURU bag of tricks ;-) :cool:

Brothers ATC wont allow cheating The Brothers ATC client is unusable unless its server program is running in tandem on the LOMAC server. In other words, if you join a MP game, fire up the ATC server and client on your machine it will fail regardless of "turning off" the export.lua server push. In short, the server must be hosting both lomac and ATC for it to work. :cool:

Perhaps the water was frozen. (J/K) I have experienced some of this strange stuff as well. Its still a bit buggy. After landing backcourse at Gudauta in the Su-33 my Jet would ignore all input commands an roll out over the ocean at locked runway alt. Then, upon quitting and rejoining, there were TWO of me. So of course I immediatly did what any good pilot would do, hunt down the imposter and destroy him. Easier said than done, the Black Sea is big and by the time you respawn and go looking (even with F2 view) it was so hard to find I realized it was invisible from my cockpit. (it did cast a shadow though but I couldn't shoot it down) Finally I gave up and about 10 minutes later the server crashed. Well sometimes like the song says: "Live and Let Die"

This is definately not right. My first guess is that gunfire is attempting to use a dx call that is broken and subsequently writes an error for it in the error log (lockon\temp\error...) if its repetitive the multiple writes to the file (HDD Access) may be impacting the FPS. Hit ctl-backspace again, and see what the details show, perhaps there is a clue there. My experience: single digit FPS is unflyable in this sim. I would try a completely vanilla 1.1 installation on a vanilla mission and see if it still does it. If so, then the trouble is exterior to LOMAC and unfortunatly could be just about anything that can impact FPS. A real bugger to troubleshoot. Borrow a friends ATI card and see if that makes it go away. That can help narrow down where the trouble is. Truthfully, I'm at a loss on this one... your system is plenty powerful to handle this.

This seems to be related to your dcom DTS system. These people have similar issues: http://www.adras.com/totally-confused.t1178-112.html http://forums.thetechguys.com/showthread.php?t=21047 This seems to be the fix: http://www.highdots.com/forums/windows-xp-help/com-catalog-disaster-1448746.html

Crusty, Your swapfile maybe fragmented even though the OS does everything it can to prevent this place the file in contiguous space the data inside this space can be placed all over the place within. Removing it, defragging the drive it resides on and reinitializing it as prophet indicates ensure a clean contiguous space for new pagefile data. Check for Lockon.exe.local in these threads and test that with your exit problem. If it works correctly then there is a DLL mismatch between your system and the mission creators systems you are joining.

See my post this thread: http://forum.lockon.ru/showthread.php?p=104203#post104203

It sounds like your PC is running a timed background process at specific intervals superceding Lockon.exe process priority. I have found that large tempory internet files (and related cookies) love to do their refresh right in the middle of a great lomac mission. Deleting these really seems to help some systems. (be sure to delete all offline content as well) Additionally, a very large swap file (virtual memory page file) eats memory handles to support it. Its best to let windows dynamically manage your virtual memory. You will also want to defrag your installation of Lock-on to minimize stutter caused by HDD access times. Your settings could be helpful here. Mine are as follows: Textures - High Scenes - Medium Terr Prld - 100Km Civ Traff - yes Water - Medium Haze - Advanced Lights - ALL Visib Rng - High Effects - Low Heat Blr - Off Shadows - Active planar Color - 32 Bit Resolut - 1024 x 768 (I match this on my desktop prior to launching Sim) Full Screen - Dark UNCHECKED (this is an important one) AMD Athlon XP 1700+ 1 GB Ram (dual 512k Sticks) Maxtor 80GB HDD 7200rmp 8mb cache Sapphire 9600xt 256mb running on 4x AGP (MSI KT3 ULTRA is not 8x :P) Saitek X45 no pedals Aopen Dual Wheel Mouse (yes, mouse drivers can adversly affect Sims) I only see stutter in missions that have been modded with things my system can't find. This tells me there is delays in Lockon.exe searching for modded weapons (LOPE) skins or textures (LOMAN) that my system simply doesn't have. Make sure if you want to play in Modded missions you intall the same mods ( I have a duplicate folder (Lock Mod) of my lockon folder that I launch with LOMAN for this purpose.

Prophet is correct. This is do to timing discrepancies between page file (virtual memory) access times and how long lockon.exe waits for the requested data. It can also be caused by memory leaks where the program pointers get pushed beyond real address space. Its interesting to me that unmoddified (lockon tweaks) installations running missions created on unmoddified machines rarely experience this and similiar (MSCVRT.DLL) issues. Make sure your virtual memory is placed on a fast HDD (at least 7200rpm 8mb cache). Please note that the page file is not defraggable hence the procedure Prophet used above. :cool:

dgram is abbreviation for datagram - an embedded ip address in the datagram was unroutable or unreachable. Cobra should check his NAT and WAN wrappers to make sure they are working correctly. The server was unable to respond to the 'invalid address'

Good Job Brothers31! I've tested this and it looks very promising for future dynamic campaigns. GGTharos and the others are to be commended for the excellent feed back in developing this tool. I foresee that radio communication skills and SA will dramatically increase in missions where this is utilized and perfected. Additionally it will open up a whole new level of enjoyment for this sim. :)

The missed descriptions just aren't there in the Common.cfg (I added them myself to my common.cfg file). The samara DX errors are common to everyone AFAIK. It appears you have never created a pilot log. The LandModelManager errors may be related to some LOMAN mod? I remember seeing the GAZ and LAP-Cable stuff in 1.02 but don't remember why it was there. Now, the CTD - Bad MSCVRT.DLL issues I imagine. Check these forums for "Lockon.exe.local" for a work around for this. :rolleyes:

I have landed deadstick numerous times in both 1.02 and 1.1 in the F15, Mig29S, Su-27 and Su-33. They all have similar characteristic effects. A) Turbines turn providing an 'Idle' sound and generator B) Gear is still operational C) Steering fails below minimum speed. So...be sure you are lined up with the centerline on TD or you will most likely find yourself needing a tow truck. D) Don't expect hydraulics (like airbrakes) to work. Also keep in mind that avionics run on batteries that are recharged by the Generators. And I believe some of the equipment has backup electrical motors (Like Gear Down). Be sure and set your Glide Speed. I have found that 200Mph in the F-15 works out very well. 350Kph in the Russians seems good, but your weight plays an important role. So...jettison what you can. Rule of thumb: Listen to Betty and check your gauges. Fuel 800 is an indicator to throttle back to 90% and find that Airbase. Keep your Altitude as long as you can and remember, the higher you are the more fuel effecient (provided you don't go past the oxygen layer ;) ) Hope this helps ;)

A quick glance at your task manager will reveal the panthers server grabbing as much as 1.6GB of pagefile in addition to the 800MB RAM to load the mission depending on what other background stuff you have running at the same time. The forced restarts are most likely do to a questionable RAM address that normally never gets used until now when your filling it up. These larger style "Big Box" missions are going to require "Big Box" Ram (2GB or more). Side Note: To prevent memory leaks endeavor to match server settings for Scene files. The Panthers server is set to High most of the time. If your comp is set to Medium leaks can occur gobbling up precious memory space ;)

Plan a diversionary hit from the opposite side of the ship to draw gun fire away from your KH-41 prior to your missile entering gun range. ;) Take some Mirages, F4's or Su-17's to engage the Hornets. :D

Alex answered the question quite nicely. Simply put, rem out the line of the Server Files section in client side Config.lua pertaining to the file you don't want pushed to the client. i.e. export.lua

It would seem that placing rem brackets [[-- --]] around the input section of the export.lua prior to running your track would prevent this behavior. Example: [[-- Input: LoSetCommand(command, value) -- (args - 2, results - 0) -1.0 <= value <= 1.0 --]]

Perhaps ED is whetting our appetite for future progression =)

Fictitious Su-33 Scenario Encouraging the Use of Twin Rack S-25: In 1987 an unnamed transport vessel (carrying what was thought to be the entire stolen lab equipment, prototypes and documentation of a working 3 TerraWatt EMP system) Developed serious engine problems approx 245Km from the Kuznetsov. The captain realizing the value of the cargo placed it in several lifeboats and had them steer to a heading away from the Kuz Fleet and toward allied support. Satellite images of the cargo transfer were relayed to the Kuz. and an intercept mission was deployed to sink the lifeboats at minimal cost before the allied support reached the area. Two Su-33's equiped with the rockets in question satisfactorially reached the targets in record time, destroyed the targets and returned safely at a minimal cost. Disclaimer: Any similarity to actual events are purely coincidental and I disavow any knowledge of any real related data or related records on file with any agency including but not limited to the CIA, FBI, KGB, CSIS, ONI, AFIA, AIA, INSCOM, NRO, DIA, DMA, USSPACECOM or any other intellegence gathering entity.

MrWolf: Rule one for me always:Save The Originals to put back if necessary. These files do not change the game core, they change the variables the game uses. If your game became "Screwed Up" then your download was most likely damaged in some way which has nothing to do with the hard work Ice, Mustang and others have put in to make our game play more playable and enjoyable. (Did you even try to make sure your download matched the orginal?) Perhaps you have some special "ED Tester" Stuff that interferes with normal installations? Just trying to Help here incase others experience similar disdain =)

Three things I noticed. 1. The file renaming as listed on the website is necessary for Hyperlobby use. 2. The program does not press the 'OPEN' or 'Server Start' button when used outside of hyperlobby. 3. Every Step seems to take a veeerrry long time - so it required much patience to see it work. Apart from that, the missions must be in the mission folder and be indexed properly (folders count in the index list). You must manually press the 'Start Script' the first time.

Turn on Radio Assist

You know, in the movie I think the Blob died...or maybe just slithered away.

Having "Wheelbarrowed" a couple times in real planes I knew right away what the steering trouble was in 25T -- its nose heavy. It seems to be modeled with a 'fly by wire' as I see definate delays in the response curve in the rudder controls which will inevitably result in oversteering. I have heard rumors that rubber quality was substandard on the real 25T's resulting in failures. But what intriques me is that on two occasions I actually broke the steering linkage trying to turn to hard. The tire didn't blow, rudders still worked, but no steering (Don't try turning in excess of 50kph). The lift problem is not imagined. Full flaps and 300kph fully loaded this bird should at least float into ground effect (don't ever plan on a softfield takeoff proceedure here) but it flat doesn't. Sim experience shows that lift occurs at approx 320Kph Full Flaps and even then it snaps up rather than floating (which scares the heck out of me with those bombs hanging low back there). The lack of lift in the model no doubt is related to not having control surface correction in a crosswind. Apparently the programmers have left us with needing much more airflow for the ailerons to begin functioning. I like that fact that the AFM allows for the weight differentials of ordinance. But there is a bug somewhere as my A/C has rolled heavy to one side with balanced load (yes I checked the fuel tanks too), Autopilot disengaged (yes checked all lights off) and plenty of airspeed (450kph) for level flight. Even after correcting to level (with great difficulty) the A/C nearly flipped when relaxing the controls. This has happened a couple of times so far. The A/C seems to handle heavy when loaded, but closely approximates the Su-25 when unloaded so I'm not sure about the model yet. I am however going to have to create banding for my trim so I can use my HOTAS instead of Keyboard (uhggg :rolleyes: ). I've never learned anything worthwhile without some level of frustration, and I ALWAYS want to know the reason (even if its my fault) thus I am sort of enjoying the challenges of the SU-25T even if they aren't quite right :icon_wink Wish I could get the thing up to angels 15 (~5000m) without having to do 5ive 360's. :tongue: All things considered, its a beast to fly and I am getting better. Haven't popped a tire in a while, but have broke the linkage and sunk the thing after take off a couple times. :cool: