-
Posts
1,970 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Downloads
Store
Everything posted by BUFF
-
just thought that "and will wait on a few more till after the DUAL-CORE AMDs'are releasd." sounded like you were planning on going x2 so I thought that I would point out the potential future problem.
-
I must admit that with modern CPU, GFX & huge hard drives I don't tweak it much at all although I could probably wring a little extra out if I did. About the only things that I do are run a seperate partition for the OS & then move the My Documents & Mail folders off of that onto another. That & use Opera as my default browser. Look what I found http://forum.combatace.com/index.php?showtopic=5118
-
I take it that you mean ASUS A8V-E. Current rev. of the K8T890 chipset doesn't support x2 processors due to a hardware problem so can't be fixed with a new BIOS but needs a new Rev. of the chipset. nForce4 boards are slightly faster (1-2%) anyway unless you have an aversion to nForce chipsets & we still have to see how the ATI chipset does in production form too. That board doesn't support SATAII features (tbh with only 2 SATA ports NCQ probably wouldn't see much improvement & the drives won't hit 1.50 Gb/s let alone 3.00)) & you might want to check that the XP120 fits - some of those caps/toroids look like they may get in the way (changed config from A8V Deluxe).
-
My XP-M 2500+ did 2.8GHZ although iirc it needed 1.85V to get up to that & a Volcano 12 at full chat. & my Venice 3200/stock hsf isn't noisy either - 2.7GHz ~40C on load (30C idle)=quite impressed btw this is the most activity the hardware forum has seen in ages, possibly ever ...
-
Interesting, if I understand it right if you had used your desktop XP2400 you would have access to all the multis upto 24 via software without a mod (if an unlocked CPU i.e. pre week ~39 2003) whereas with the XP-M you need a pin-mod. I used to run an XP2400+ at 2.4GHZ, maybe you should pop yours back in? Going for 2800MHz next - btw this is on the stock HSF!
-
Doesn't work for everything though. I tried it once for something & it didn't make a blind bit of difference - think that I ended up disabling fast-writes iirc.
-
been doing some more reading up Have you seen this ? "enable mutliplier on-the-fly adjustments from operating system (can be done under full load) fully stable operation, multiplier change designed by AMD be able to change multiplier in whole range of 3x - 24x without single wire To this date function verified on following chipsets (please report other): VIA: KT133A, ... " Thought that you might like to see my new toy - just had it a few days (btw it's actually at 1.4V - CPU-Z seems to be wrong).
-
I'm not so sure about that (afaik all you needed was a CPU with a 13x or more multi & even an XP-M 2400+ gives you that) but even then it's $60 versus a 1/2" piece of wire & a few minutes work ... Interesting read though, thank you.
-
I would have gone with an XP-M 24/25/2600 for far less (I had my XP-M 2500 doing 2.8GHz) or an AMD64 for very little more. Of course AMD64 would have needed a new board, new RAM .... I could have told you about pin-modding, CPUMSR etc. too. Still it's a good read so far so eagerly awaiting next installment :) - I reckon the SDRAM is probably the biggest bottleneck?
-
You could always try Normal rather than Easy .... Just to confirm then that it isn't bobbing in normal flight but whilst pulling hard turns?
-
Is this just at extremes of envelope (e.g. hard turns in either vertical or horizontal planes) or even in relatively level flight? There were quite a few fm changes in the last patch, 1 of which appears to be limiting what you can pull & you can get a sort of elevator fluttering effect. It's been reported. If it's in relatively level flight I'm guessing by the old hand statement that you are using the hard fm setting?
-
These days you just need to drop the skin folder into the aircraft folder. I don't know about the black merc skin but if the SEA was Galanti's just extract (using WinRar) the SEA folder to your \Objects\Aircraft\F-100D folder alongside FrenchSilver1 & USAFSilver1. That's it. Now when you launch the game & select the F-100D you should be able to select that skin too.
-
Think that I already posted the link to Andy ush's weapons delivery article at SimHQ in 1 of your earlier threads. In kreelin's mission editor you will also find a simple ballistics calculator for working out height/speed/weapon drop ranges to targets. dfang was also working on something different. http://forum.combatace.com/index.php?showtopic=8574
-
You probably need to extract the .ini from a Cat using the SFP1E extraction tool (available in the dl section here).
-
The gun editor runs in Win98 compatability mode (or of course on Win98). Tbh you probably don't need the gun/weapons editors as most common weapons are in the Weapons Packs & most aircraft are released with realistic .inis for weapons use (or if not someone in the community will do it & post it). Similarly building your own terrain is a lot of work. We already have DRV, Europe, Madagascar, Bering Sea, America NW etc. terrains to use & some more terrains coming shortly too. Where do you want the campaign set as maybe the terrain is already available? There's a Campaign Tutorial in the "SF editing" sticky if you haven't already found it http://forum.combatace.com/index.php?showtopic=4078
-
Instalation problems
BUFF replied to OengusAnBearMor's topic in Mission/Campaign Building Discussion
.rar is a form of compression like.zip but superior. You need to use something like WinRar to decompress them properly. I thought that in Gaelic/Celtic bear was art/artos/artus etc. or math/mathuin/ mathghamhain etc.? -
Pretty much everything is usable in SF P1 & WoV - not 100% but well into the 90%s. Usually if something is only usable in SF P1 or in WoV it is because it needs to use a file normally only found in that - e.g. an addon aircraft that uses the F-104G cockpit will normally only work in SF P1 because WoV doesn't have the F-104G & therefore the cockpit files that it calls (of course it is possible to copy them over ;)). SF P1/WoV are not designed to be as "hardcore" sims as Falcon 4.0 & of course the sytems of the aircraft in the period that the stock game represents were nowhere near as sophisticated as the F-16's anyway. In air to air search mode you should be able to move the cursor over a blip using the Home key (or whatever button on your joystick you may have mapped to Next Radar Target) & then to lock using Insert (or whatever button you have mapped to Acquire Target). Boresight sounds the same in Falcon as in Sf/WoV. You might find this useful http://www.simhq.com/_air/air_061a.html You can't currently lock anything in air to ground mode radar itself - nevertheless there are ways of using guided weapons. You might find this useful for dumb weapons http://www.simhq.com/_air/air_055a.html Note: both the SimHQ Wep Del. articles were written a couple of years & several patches ago so some things have changed. Also depending upon how you have your different preferences set has an effect upon what you see.
-
Welcome Maddog, the more the merrier :) I hate to say it but pretty much anything you want can be found if you here & at SimHQ. SF P1 & WoV both use the same Third Wire game engine but differ in default terrain & plane set. Yes, you can add carriers to SF P1 (I know that there are details for this on the forum as I posted them while talking a few others through). Yes, you can have campaigns with other planes but you neeed to download & install the other aircraft (assuming that they exist) & do some minor .ini editing to make the campaign use them. Of course if you are lucky someone like Mk2 may have got there before you & released a pack with what you want all neatly packaged. If you can be more explicit in your radar problems maybe we can talk you through it (again I know it's all been done before if you search).
-
Instalation problems
BUFF replied to OengusAnBearMor's topic in Mission/Campaign Building Discussion
Hi, You need to be more specific about your problems. We need to know your patch status, which particular carriers you have installed , are these in single missions or missions that you are making etc. I must admit that I've never tried to install/use the nukes so I'll leave that for someone like fubar_512 btw a good Gaelic name there but I'm trying to work out what it means - bear is throwing me (Angus the big/great ?) ? -
All you have to do to make any AI aircraft flyable is to add the relevant entries into the data.ini Taken from the stickied above "SF editing notes": "Flying New (previously non-flyable) Aircraft Previously non-flyable aircraft can be flown as follows. Say you want to fly the Mig-21Mf, which is in \Strike Fighters\Objects\Aircraft\MiG-21MF Open the *.INI file in that folder. It will look like this: [AircraftData] AircraftFullName=MiG-21MF Fishbed-J AircraftDataFile=MiG-21MF_data.ini LoadoutFile=MiG-21MF_loadout.ini Change it to look like this: [AircraftData] AircraftFullName=MiG-21MF Fishbed-J AircraftDataFile=MiG-21MF_data.ini CockpitDataFile=F-104G_cockpit.ini HangarScreen=MiG-21MF_hangar.bmp LoadoutImage=MiG-21MF_loadout.bmp LoadoutFile=MiG-21MF_loadout.ini The MiG-21MF will use the F-104G cockpit. Now use the hangar.bmp and loadout.bmp files from MajorLee’s flyable Su-7, and rename them MiG-21MF_hangar.bmp and MiG-21MF_loadout.bmp, in the MiG21MF subdirectory. That's all. The MiG-21MF will now be selectable." The cockpit from Armourdave's Su-17 should be pretty similar I would have thought so if you get that addon you could then use it's cockpit entries for your Su-7.
-
You mean http://forum.combatace.com/index.php?download=1289 that I've just approved? ;)
-
The Banana is being made by RussoUK2002 - hopefully it should only be a couple of weeks. Another person is making a model of Ark Royal so we should have the proper carrier to fly from ;)
-
It's back http://forum.combatace.com/index.php?download=1270
-
1) your SF is fully patched? 2) some details of your system & DX that you are running might help. 3) are your gfx card drivers up to date - I had to update recently to latest nVidia 71.89 due to some issues. 4) can't really see a problem in the attachment?
