

DeltoBrava
Members-
Posts
16 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by DeltoBrava
-
The interval thing may be true but the fact is I've gotten this problem 5 minutes into a fresh new flight before. Has happened to me multiple times on the first campaign mission. I follow the checkpoints to the first group of targets at the base of the mountain on the left and by the 3rd or 4th target my laser is good as useless. Landing to repair does nothing and nor does trying to cool it off. The intervals may be implemented but there is definately a glitch in the system somewhere or there is a "your laser will not work" malfunction that is hidden and is set to malfunction %10 of the time.
-
I don't know why you would need to have a buddy? All you need to do is set it on manual mode, lock the target with your laser, and you're all set to make a 15km shot. I've made plenty of 15km shots with the 25-ml and I believe it has a 20+ km range, but the map I made these shots on had fog and I'm not sure if that's what was making my laser lock on at exactly 15km and not sooner. I never did try to fire it beyond 15km, I would just wait for the laser to lock because I wasn't about to manually hold the gate on a target for 5km straight. On auto mode I find that the 25-ml fires no sooner than 7.5km while the vihk fires at a further distance than that, around 8.0 - 8.5km. I always shoot manual mode because auto mode just handicaps your range.
-
Yes. Works whenever I do it and it does it instantaniously.
-
My computer specs are nearly identical to the thread starter. Differences... 1. My Nvidia driver is about 8 -12 months old 2. I have SP2 3. XP Pro 64-bit (I don't think that matters though) 4. My game runs fine I would try getting an older video driver ( I'm not sure how old the last driver you posted is), not just rollback 1 or 2 drivers and also try to get SP2 instead of 3 I always keep drivers on my computer roughly 8 - 12 months old because new software/drivers always break programs it seems.
-
As far as I've seen, everyone in the game with Vista (32 or 64) is unable to alt-tab without it crashing the game or screwing it up in some way. I run XP 64-bit and alt-tab works fine.
-
Game exits when helicpoter crashes/blows up
DeltoBrava replied to Slayer's topic in Bugs and Problems
I have a Logitech Freedom and also got the same problem the very first flight, and crash that I had. I had all the graphics setting on high with cockpit resolution on 512 and water or normal. I only used these settings for my very first time. When I crashed my heli, the game crashed too. I then set everything to medium with cockpit resolution on 256, and visible range to high. I haven't got this problem again since my first crash. -
I was playing a campaign mission (with labels on) and happened to fly over two T-80's who looked to be in perfect condition when I thought I had cleared the entire area of tanks. I circled back thinking it must of been some kind of model glitch because they appeared to be in perfect condition. As soon as I was about 50 yards away they fired their main gun and took me out. Both of these tanks had no labels on them. This was on level ground, there were no hills, I could see them, and they could see me. I had labels enabled for this mission so don't always trust them as they are obviously glitched sometimes.
-
I did the following... 1. Started multiplayer game up 2. Alt+tab 3. Selected DCS, set affinity to both CPU's 4. Went back into game 5. Everyone was jolting all over the sky for 30 seconds 7. Alt+tab 8. Disabled the second CPU I had selected the first time around 9. Went back into game 10. Game was fine I have Windows 64bit Conclusion: Manually setting DCS to both processors isn't good...
-
I thought this problem was only with me because of my joysticks calibration. This does happen to me frequently even a few minutes after re-calibrating. Bug?
-
It's a confirmed bug. Someone in the help section got the thread for me. I was also getting the laser switch reversal glitch when this was happening to me. Laser off is actually on and laser on is actually off, ontop of that the missles nose dived. These 2 bugs = mission failure guaranteed
-
Thanks, atleast I know it's a confirmed bug now. Just beat campaign chapter 1 - mision 1. Got to mission 2 and it happened to me on the last 10 or so targets. I was forced to try and sneak up on 2 zu-23 gun placements with my cannon which didnt work because it was level ground all around them. The checkpoint was right near them so I had to do a suicide dash right between them and went down because I took 25 rounds. Hopefully this bug is fixed because it kills any chances you have of beating this game without immortality on.
-
zu-23 emplacements, t-55 tanks, fuel trucks, stinger man pads, and something that looked like a bmp. The target didn't matter in my situation, the vihks refused to travel the full 3km to the target. They loved the taste of dirt so they kept nose diving into the ground for no reason.
-
I was playing the first campaign mission and upon switching targets all the sudden my vihk's started to fall short by roughly 1km. I thought maybe my laser was burned out so I turned it off, flew back to base and re armed. Came back and tried targeting 5 different targets and my missles would continue to fall short after locking on to the target. I thought maybe my laser still needed to cool down more so I flew around for 5 or so minutes and repeated the process. Missles still fell short. I figured something must be damaged even though I had not been shot at. Headed back to the base to repair. Shut off all my engines and sat there for about 5 minutes. Started everything back up, made sure my entire weapon system was reset, then started the weapon arming process over again. Got to my targets and my missles were still falling short about 1km. These targets were all within 3 - 5 km and were not out of range of the vihks. Even with targeting off, the vihks would still nose dive into the ground after going a certain distance (about 2.5km), where as before I made some 8km shots without locking the targets, but just by holding the schval on the target. I have played countless hours online and have never seen this happen with the vihks. Is this a bug or is there something I'm not aware of?
-
I was playing the first campaign mission and upon switching targets all the sudden my vihk's started to fall short by roughly 1km. I thought maybe my laser was burned out so I turned it off, flew back to base and re armed. Came back and tried targeting 5 different targets and my missles would continue to fall short after locking on to the target. I thought maybe my laser still needed to cool down more so I flew around for 5 or so minutes and repeated the process. Missles still fell short. I figured something must be damaged even though I had not been shot at. Headed back to the base to repair. Shut off all my engines and sat there for about 5 minutes. Started everything back up, made sure my entire weapon system was reset, then started the weapon arming process over again. Got to my targets and my missles were still falling short about 1km. These targets were all within 3 - 5 km and were not out of range of the vihks. Even with targeting off, the vihks would still nose dive into the ground after going a certain distance (about 2.5km), where as before I made some 8km shots without locking the targets, but just by holding the schval on the target. I have played countless hours online and have never seen this happen with the vihks. Is this a bug or is there something I'm not aware of?
-
Problem Solved.
-
I created a new user after installing the game. Only one user profile was on the game. I did a mission and died... it then said my user profile could not be used anymore cause my player died. I made a new user profile of the same name and deleted what I thought was the old one. I think the problem is I deleted the new one, leaving the "non-playable" one. Either way I don't know why it just blocks me from going in because now I can't make a new profile. When I start the single player game now it gives me this error: ..\blackshark\modules\me_logbook.lua:141: attempt to index field 'player' (a nil value) *Note: this started happening after "my player died" I want to know if there is any way to fix this without re-installing the game. There are too many reconfigured controls for me to re-install it and if that is the only option where can I find my saved controls profile? I did save the controls so I can find them if a re-install is needed.