Silent Warrior

shaman: Yep, so I do believe it's the HD. At least those are fairly cheap... Prophet: Oopsie, those were the U-DMA-settings. PIO was at 4 all around. Now set to 3 for HDs, at least, it gives me a few more seconds of play in F4AF. I'll set it even lower and hardly even touch the thing before I can buy a new HD. Hopefully that'll sort me out.

AAAAH! AGAIN! IT WOULDN'T LET ME POST NOW EITHER! #¤"#¤"@€$! :mad: GRAAAH! Alright, in order... AGAIN... Thomas: Heh! Well, that does sound reasonable. Though that HD isn't the oldest piece of my rig, it has been put through its paces, I suppose. But it's my C-drive, it must be a real *beep* to switch just like that! Well, at least they're reasonably cheap... As for the 9700, it does smell kind of funny... Not torched, but all w3rd-like. Like some sort of really warm goo. I was looking to upgrade like soon, but I'd be gunning for PCI-E then... Prophet: Downloaded, will install when opportunity arises. I'm sort of busy for the next 10-11 hours, actually. The soundcard is back, and I agree that it doesn't seem to be the problem. At least I won't be embarrassed, always something. My harddrives are using PIO 5, I think. Or was it 4? Anyway, it uses a higher digit than my CD-drives (PIO 2). Both default-settings as I haven't dared touch them. Will see what can be made to happen. Mustang: I didn't bother counting the slots, but I have an IRQ-conflict on another machine (weird that, it used to work, honest, it did!) and this looks nothing like that. Different hardware, true, but I don't think IRQ is the issue... unfortunately... Alfa: I tried, but it wouldn't let me. :p zenTera: nForce? Pff, newfangled twinklies! :rolleyes: I happen to have an ASUS P4T-E. Latest BIOS-update being a beta from november 2003-ish, latest 'official' release from august 2003. Latest general download is Intel's wossname-installer v. 5.10.sumthingsumthing. Yay to be me! I'll look over the HD next. Stay tuned... *Marwin-mode engaged*

Alright, that's it, I have tried to post about this problem THREE TIMES, and I wasn't allowed to! Can I post this? OK, good. Since I've wrote a quite lengthy post about this TWICE, you'll have to make do with a shorter version. I bought an X-Fi Extreme Music this Saturday. By Monday I couldn't play any games because my machine freezes a few seconds into 3D-rendering. X3, F4:AF, X-Fi Splash and CCC have been tested and all freeze. I make sure the drivers are all installed as they should be, no change. I yank out the X-Fi and go back to the onboard soundcard, no luck either. When I get this freeze I can hear some sort of 'thunk' and the HD-activity light goes full throttle. I have contacted Creative about it. In case it's something wrong with my Radeon 9700, I've also contacted ATI. No concrete help from them yet. If this has torched my 9700, I'll have a fit like you wouldn't believe. It cost me $600 back then (2002)! There's a possibility it's my RAM buckling, it's just as old. (512 Mb RDRAM PC2700) Any thoughts?

Gazehound: Yes, I know, but I like to keep it around for situational awareness. Once the shooting starts, I usually switch over to the real deal - MUCH easier in CAC, actually (luv teh BORE!). Bugger me if I see if anyone's on my tail, but at least the radar-modes work like I expect them to. And I DID try changing the payload (you'd think the Vikhrs would help). The only change was that my wingman bit the dust SOONER... BRD: Hm... Then maybe Easy Flight would set me up a treat? Bah! I pronounce thee BUG! Wonder how tricky it is to fix, anyway... They DO work with Easy Radar, though. Most obvious with the 25T (duh), but regular 25, using Kh-25, snaps to a target in normal Easy Radar-fashion. Well, sort of. Turning on the laser after that will screw you up something fierce, but when all is well and good, ER works with a Su-25. Tricky, but still.

If you have that utility that extracts your Starforce-registration, reinstalling doesn't take all that long, really. But maybe you should have a look at your registry before doing that, see if the entries are pointing at the correct directory, if they exist at all.

Now, put that minigun back down, son. So, Easy Radar first. When I'm flying an F-15, I notice the target-acquisition doesn't work right. I hit Tab and get that red square all well and good, but the green TDB belonging to our beloved onboard radar stays in place. And by that I mean that the TDB stays right where the target was when it was targeted and doesn't move an inch even when said target blows right past you, while the red square works perfectly. It works as it should in MiG-29, Su-27/33 and Su-25T (it's always hard to tell with the regular Su-25). And not in F-15. Grr. Now for Immortality. It simply won't apply to the Su-25s (T and normal Frogfoot). I have declassified campaigns and set it as an option - as well as Easy Radar, which applied just fine, same as Crash Recovery - but it didn't help at all. I somehow managed to get away from the Iglas in Su-25t_campaign mission 4 (and dropped FAEB, KAB Kr-500 and rockets on the damned sons of... anyway), but I can never get past the first mission in the Flaming Cliffs-campaign. If I'm not shot down on the first pass, I either crash or get shot down during my next pass. I'm really starting to hate Iglas with a passion. (Yes, I am that 'reckless'.) AND missions pitting you against all hordes of hell with just a bundle of rockets up your sleeve.

anivanov: Ah, I bet that's the reason. Or one of them. Try reinstalling, that helped me get that self-shading back. :cool: Teh pretty! Anyway, reinstalling will put those registry-entries back in place. Before you do anything drastic, though... You didn't happen to move LOMAC into another directory after you installed, did you? Just plain cut-n-paste?

Uh-oh. Loads of missing stuff can't ever be good, but shouldn't the game crash on mission-load instead of mission-exit then? W3rdness. Well, I'm pretty much out of ideas here. ED, where art thou? Perhaps you could try disabling whatever mods you have installed? Does your 9550 have any freaky issues with anything, by the way?

... Ah. No wonder you don't have FC, then. :) I wasn't referring to the error-message, though - I'm after the error-LOG (ED are in the best position to make heads and tails of those memory-addresses, not ordinary mortals like myself). In your Lock-On directory/folder (default-ish C:\program\Ubisoft\Eagle Dynamics\Lock On) there's a subdirectory called temp. In there you should find a file named error.log. It doesn't just log errors, though, I can also see campaign-dates (start-hour/day of mission), some something-somethings, 'Loading new Su-25T flight model', etc. If it's anything like reasonable FS2 Open debug-spews, it's the last lines you're interested in. I won't be careless and suggest it's only the last line, now, it might be something more important a step or two - or maybe even 14 - above the last line that prevents that crucial little thing at the end to execute. To ED: More time-stamping in the error-log, PLEASE! ;) I noticed the one at the top, but I can't be sure it's all from one crash. 233 kb it all weighs in at. I don't play just one mission when I play, so with the current logging I'm not very sure what I was doing when something in the middle sets off the alarm.

I looked at your Dxdiag.txt in that other topic. Which Catalysts are you using? You have installed them properly, I hope? I'm no expert on this sort of thing, but many dlls appeared to be of different versions. Regardless, I find it unlikely that would be the issue. (But you'd be amazed what improper driver-installation will do to your Edge of Chaos. :) ) Crash on mission-exit... Must be the assembling of the Debriefing, then? What does your temp/Error.log say? (I found half a billion - no exaggeration! - of Failed to create Pixel Shader, by the way. Must be why I'm not getting any self-shading.) See what happens if you uncheck the Write protect-attribute. Maybe the Debrief has to be written to some file that's accidentally locked. When you have the time, see what ScanDisk and Defrag yields. And GET THAT PATCH. Good for your health. :D

If the third mission in the F-15-campaign still crashes, I'd really like to see it fixed. (Haven't tried for a good long while. Firing LOMAC up takes so damn long on my system it would be more pain than it's worth.) Also, if there is a way to convince my rig that it doesn't have to spend half the day loading a mission, I'm all ears. (Well, it usually only takes 1-4 minutes when all is well and stuff is cached, but still. I have had the time to devour lunch in between clicking Fly! and actually starting the mission.)

I believe you want at least the 1.02-patch. Well, as soon as you're done with the training-missions, that is. I have absolutely no idea about your crash, though. Just to clarify, you are in a mission, hit Escape and then click Quit/press Q? And then WHAM? Not Close in Debrief or upon return to main menu? Were you playing a campaign at the time?

I have an SB Live 5.1-thingy (I have no idea if I really get 5.1-audio, though - damn sound-formats not keeping up :p ), and no such problems. :icon_eek: Another thing I don't have is brute CPU- and RAM-force...

Hm... Maybe I SHOULD get my act together and give the Frogfoot a proper abuse... :D

Um... You guys didn't invent a tradition of new-year's-pranks or anything while I've been away, have you? That physics card sounds just too damn fine to be true... PPU soonish, eh? Well I'll be...

An' I'm thrilled to see a new campaign. Whee! :D

I really can't begin to understand SCOTSMAN's post, so I'll throw in one of my own. EOS, not an active sensor, we're all clear on that. As I understand it, however, it tracks heat signatures. Picking up radar-signals is done with RWR, isn't it? I'm not going to claim to know anything about RWRs and missile-launch warnings, but in Falcon 4, I never got a warning about R-27Ts on the RWR. As IR-guided missiles just home onto a heat-source, it can't be seen on RWR, right? Maybe if there was some sort of missile-tracking radar-thingy...

I have a similar problem (also using X45), but for me it's not a horizontal drift, one of the engines (always on A-10, happens with no other craft) doesn't work. I'm not very good at describing this sort of thing, but I take off all normal and stuff, use the autopilot, and then one engine croaks when autopilot is turned off. Comes back up when I turn the autopilot on again. Talk about a thorough ruination of your gun-aiming... Could this be the case for you too?

I see. So Easy Rader works as it should. Alrighty then. B_R_D: Hm... It's not at all impossible that's what happened to me... The Alt-J-part, that is. Peculiar bug.

I want the CPU/RAM-might to use this... :(

Now, don't you look at me like that. I meant ACCIDENTALLY infinite ammunition for the GAU-8. More on that later. When you have Easy Radar turned on, it's simply impossible to use the Maverick. You press Tab and get one target, fire, boom, whee, then press Tab again. Nothing. You have to go to normal radar (Shift-I) and find your next target the right way. Any chance of making that work like advertised? I mean, it's not the biggest of deals to me - as long as I've got labels or that priority-target diamond, I'm an apocalypse with Mavericks in normal radar - but it stings my eyes. As for the accidentally "infinite" GAU-8 ammo... Well, I say infinite, it was actually like this. I flew around a combat zone smacking vehicles all over the place. Soon enough I had expended all stores and drained my gun-ammo as well. As I reach the 0-mark, guess what? Congratulations, you have won our ammo-lottery, and have been given 65536 bullets! :icon_eek: This doesn't happen every time, and no, I didn't have infinite weapons turned on. Was this just a hickup on my side, or a real bug?

:p Meanie!

What Catalysts are you using? I'm using a Radeon 9700 Pro and Catalyst 5.5 (or whatever they're up to now), and that's an older card then the 9600, if I'm not mistaken. Still no such problem. My firsthand advice would be to uninstall the ATI-drivers throughly, taking care to delete any remaining files, or send them to the garbage bin. From then on, follow ATI's installation instructions and see if that takes care of it.

For us only halfwit flyboys (read as: I ain't no ace, son), any reduction in difficulty is welcome. Especially in a campaign, where progression demands a rousing success. Wanna cater to me or not? :)

Ow... Let's see if I've got it right: You want to edit the .cmds somehow? I think only ED can do that - if it's a custom-tailored fileformat, chances are ED are the only ones who have the appropriate utilities. It might be a bit of a bugger having them release it to the public.