4.33 Issues (Known or not)
-
Happy new year
16 Gb RAM
64 BIT win 7
64 bit FBMS.db
Happy new year too!
My thought was you are using 32bit. No further ideas, sorry.
-
I always do my DTC with the WDP because I need extra information for my flight planning. Then, I just clear everything before I save the DTC, then I check the map to see if my PPT / steerpoint / lines are correct. Then, I just load it into Falcon.
-
I always do my DTC with the WDP because I need extra information for my flight planning. Then, I just clear everything before I save the DTC, then I check the map to see if my PPT / steerpoint / lines are correct. Then, I just load it into Falcon.
Are you doing all of this in WDP with the sim open in the UI and campain running after saving the campaign? Or, are you saving the campaign and closing Falcon down first?
-
Running at the same times and alt-tab.
-
never had the problem. how do you reproduce it?
we can’t fix something we can’t reproduce.There are two I think unrelated issues. Sometimes a very different L/L value sneaks into the DTC probably from another mission often in the middle of a flight plan. The word going around is that it may only affect users which have Balkans theater installed. A survey should be taken to see if Balkans users and users that have seen this issue are the same group. I’ve seen it once or twice and do have Balkans. I might have also experienced the issue on not the first sortie of the session as dawg mentions.
The second issue that Agave and I mention is that manual coordinate entry into the system can be not verbatim but just close. I was unable to produce it in the nav TE apart from the very boring base 2 rounding error on the last digit. Of course if there are any system deltas it’s reflected in the numbers so CZ is pressed for good measure by all means. It might have something to do with the quality of the align so deserves to be tested from ramp which I’ll do as soon as I fix my joystick load order grrrrr.
-
[To the moderators; if this should be in tech support could you place it there?]
Back to confirm issue again, I had issues with my graphics card which was preventing me from doing any testing, finally got that straightened out. So I tried the Tomcat again in both 32bit & 64bit modes and have no difference with the result. I have my frame rate displaying in the pit so I can watch to see if that was an issue. Its around 15 fps on the ground when things happen, FYI 15fps is good on my machine. It drops to a claimed 2 or 3 fps when the aircraft is exploding on the flight deck, so I don’t think the issue is directly due to having issues due to FPS. And its the same every time, right side drops and then the gear seem to unlock and the aircraft drops. I get the same result no matter what position I try for. I was wondering if maybe the carrier itself was the issue so I added another flight starting feet dry, and I get the same result. I recorded an ACMI for it, is that useful or should I try FRAPS?
For reference I’m using Vista x64 sp2 for an operating system on a hp a6700y, which houses an AMD Phenom 9150e quad core processor. I added a power supply a while ago to it so I could install a real graphics card instead of the integrated chip it came with, and currently I’m running a Radeon HD 3800 for graphics. Yes I’m aware this thing is lowly but it works well enough.
-
Sometimes a very different L/L value sneaks into the DTC probably from another mission often in the middle of a flight plan. The word going around is that it may only affect users which have Balkans theater installed.
I don’t have Balkans installed, and I’ve experienced it in Korea. Just earlier today it happened in Korea, the waypoint for my target and the IP where far away from my actual target, presumable the target for an earlier mission, although I’m pretty sure I never made any precision target for any mission to that location…
The second issue that Agave and I mention is that manual coordinate entry into the system can be not verbatim but just close. I was unable to produce it in the nav TE apart from the very boring base 2 rounding error on the last digit.
Don’t know if it’s the same issue, but when my waypoints where in the wrong location in my mission today, I tried to enter the correct coordinates for the waypoint in the DED (WDP had the actual coordinates, and I’ve checked since with recon that they match). Entering coordinates went ok, but the steerpoint was still several miles away from the target (even after I pressed CZ on the MFD to clear any offset). Not as far away as my original waypoints, but far enough that I had to do quite a bit of searching before I found my target.
-
Pretty sure you messed up your DTC if your INS has been correctly align.
-
Pretty sure you messed up your DTC if your INS has been correctly align.
That is of course possible. But what in the DTC would be wrong?
I still have the WDP open from that mission, and in the DTC section it does list the correct coordinates for the target waypoint. And none of the waypoints are precision waypoints.
I could have possibly picked a different mission inside BMS than I thought, and hence got the waypoints for a different mission. But in the debriefing I did get a successful mission for destroying the target I was supposed to, so I don’t think I flew a different mission.
About the wrong coordinates when entering them I’ve tried several times to reproduce with the same location now, and it does work correctly. It’s possible that I may have simply made a typo with coordinates, but can’t say for sure now.
-
What can hapend, is that the DTC saved is not the right one. Depending of the mission type, it could be stored in the pilot.ini file and on the mission.ini file. Then, check both with the WDP when reset the DTC.
-
In short WDP is mandatory and falcon Dtc might cause troubles?
-
Nope, but is more easy to control what is inside the DTC with it. That’s why I use it.
-
What can hapend, is that the DTC saved is not the right one. Depending of the mission type, it could be stored in the pilot.ini file and on the mission.ini file. Then, check both with the WDP when reset the DTC.
It was a campaign mission, so it should have used the pilot.ini file, right? That’s the one I viewed in WDP, no precision waypoints there.
-
No, in 4.33 it could be also saved in a campaign name.ini file. That’s the difference.
-
No, in 4.33 it could be also saved in a campaign name.ini file. That’s the difference.
Oh, wasn’t aware of that! That’s a change with 4.33? When will it used waypoints from one as opposed to the other?
Checking the ini file for the campaign now though (I haven’t flown any missions since), and it appears to contain just the same coordinates as the pilot.ini file (the correct ones, but not the ones I got in the cockpit). And no precision waypoints I can see there either.
-
Avoid CH13 and prefer one of the Tactical Freq … CH13 (like CH14) is nothing realistic (sort of massive broadcast with heavy traffic).
Apologies for dragging up this old post, but I switched from Ch13 to the tactical frquency and AWACS was still spamming like crazy. It won’t shut up and chatters constantly throughout the sortie unless I detune AWACS completely.
-
Apologies for dragging up this old post, but I switched from Ch13 to the tactical frquency and AWACS was still spamming like crazy. It won’t shut up and chatters constantly throughout the sortie unless I detune AWACS completely.
In the ‘Settings’ section, un-select ‘UI Chatter’ and see if that helps.
-
I had that happen to me I had to clear all targets in the data Cart re did the mission and it worked fine
-
UI Chatter is an option if you listen to the radio while in 2D. AWACS “Radar contact…” type messages are spammed on 307.3Mhz which is ch13. “I switched to the tactical frequency” needs more info. What frequency/ch is tactical?
-
UI Chatter is an option if you listen to the radio while in 2D. AWACS “Radar contact…” type messages are spammed on 307.3Mhz which is ch13. “I switched to the tactical frequency” needs more info. What frequency/ch is tactical?
I think you have to set that up Fred. BMS User Manual, “7.6.2 Radios in the Falcon4 BMS World”. It does not specify which channel guard is or what reference channel should be used, but does specify flight package settings and frequencies. So it looks like you will have to set up (pre flight) your TAC channel.