rfresh

>[edit: subject - AGAIN please list the product when asking a question (as outlined in the forum's FAQ)] What am I missing here? This is the feelThere forum and I'm asking about the Phenom 100 product...what else do you need to know about the product? What am I missing?

On the Phenom 100 is there a hot spot I can click on to hide the control yokes? Thanks... [edit: subject - AGAIN please list the product when asking a question (as outlined in the forum's FAQ)]

Solved: I had to wait about 30 seconds before GPU came online...thanks...

@scoob Thanks for the tip but that didn't help. I have the feelThere Phenom 100. There isn't a setup panel somewhere in the sim where I can enable ground power for it?

The GPU switch is dead...I cannot get it to work....its display is always black, no AVAIL light. How do I fix this? Thanks... [edit: subject - please list the product when asking a question (as outlined in the forum's FAQ)]

Once again Pete, you assume everyone knows FSUIPC as well as you do...I have been away from it for many months and do not remember all of of the details about how to use it's logging features, what 'S8' stands for, etc. I'm finished here.

Yes those values are of the over head panel. Those overhead values are relative to the default VC view...which is as if you were sitting in the Captains seat looking forward...so it sounds like it worked for you via Lua. And yes, zeros puts you outside, at the a/c reference datum point...again looks like it worked for you Pete. As for A860 being last, remember I was using Paul's DLL so maybe he can confirm his code is sending A860 last. Maybe it isn't. But, over all Pete, it looks like your 't' version is working for this DOF() call. I'll continue to work with Paul and see if I can get it to work for me with my test app and his DLL wrapper. Remember, I have already got this working in my main app using SimConnect directly. If there is anything else you would like me to test for you Pete just let me know.

Attached... FSUIPC4.log.txt

How do I enable the log and what folder is it in?

Sorry Pete...I don't see any changes when I use your 't' version.

That was it -- I had to get the updated DLL in there -- still had the old one for some reason. OK, so the test app runs now. I took these values cameraData.fDeltaX.Value = 0.50f; cameraData.fDeltaY.Value = -0.37f; cameraData.fDeltaZ.Value = -0.47f; cameraData.fPitchDeg.Value = 52.00f; cameraData.fBankDeg.Value = 0.00f; cameraData.fHeadingDeg.Value = 0.00f; from my Captain Sim 777 VC overhead panel view. From the captains seat position looking straight out the windshield, I clicked the button and expected to see the camera view change to show the over head but the camera only bumped up a very small amount from the captains view. So, I'm not sure why. I did get a small test app working extremely well using SimConnect last week, so I am familiar with the VC camera views. In my SimConnect app, once I set a view, I can move the camera around just by using the DOF() call so that's why I was thinking the FSUIPC call would respond in a like fashion. Let me think about this for a bit and see if I'm forgetting to setup something before making the camera call..thanks for your help... I'm attaching my main form file so you can see what I did. Form1.zip

I still get the same error: This line private Offset<SimConnect6DOF> cameraSetRelative = new Offset<SimConnect6DOF>("camera", 0x86A0, true); is giving me a compile error: A first chance exception of type 'System.NullReferenceException' occurred in FSUIPCClient.dll Additional information: Object reference not set to an instance of an object. Here is my code (following your instructions): using FSUIPC; using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Linq; using System.Text; using System.Threading.Tasks; using System.Windows.Forms; namespace TestApp { public partial class Form1 : Form { public Form1() { InitializeComponent(); } // declare the structure of 6 floats public class SimConnect6DOF : FSUIPCStruct { public FSUIPCStructField<float> fDeltaX = new FSUIPCStructField<float>(); public FSUIPCStructField<float> fDeltaY = new FSUIPCStructField<float>(); public FSUIPCStructField<float> fDeltaZ = new FSUIPCStructField<float>(); public FSUIPCStructField<float> fPitchDeg = new FSUIPCStructField<float>(); public FSUIPCStructField<float> fBankDeg = new FSUIPCStructField<float>(); public FSUIPCStructField<float> fHeadingDeg = new FSUIPCStructField<float>(); } // declare the offset, using the structure as the datatype. Offset starts at 86A0 private Offset<SimConnect6DOF> cameraSetRelative = new Offset<SimConnect6DOF>("camera", 0x86A0, true); private void button1_Click(object sender, EventArgs e) { // set the values to write SimConnect6DOF cameraData = new SimConnect6DOF(); cameraData.fDeltaX.Value = 12.34f; cameraData.fDeltaY.Value = 12.34f; cameraData.fDeltaZ.Value = 12.34f; cameraData.fPitchDeg.Value = 12.34f; cameraData.fBankDeg.Value = 12.34f; cameraData.fHeadingDeg.Value = 12.34f; // Assign the new structure to the offset value cameraSetRelative.Value = cameraData; // Process the group containing the 'cameraSetRelative' offset FSUIPCConnection.Process("camera"); } private void CameraWriteStructure_Load(object sender, EventArgs e) { FSUIPCConnection.Open(); } private void CameraWriteStructure_FormClosing(object sender, FormClosingEventArgs e) { FSUIPCConnection.Close(); } } }

I got the TestApp created with your code. I'm getting only one compile error: Error 2 'TestApp.Form1.Dispose(bool)': no suitable method found to override c:\users\fresh1011\documents\visual studio 2013\Projects\TestApp\TestApp\Form1.Designer.cs 14 33 TestApp on this method, the Dispose method name: protected override void Dispose(bool disposing) { if (disposing && (components != null)) { components.Dispose(); } base.Dispose(disposing); }

I tried copying all of your code into a TestApp but had many errors so I put your code into my main app. Let me try the testApp again and check your DLL location.

OK...its set to: C:\FSUIPCClient3.0_BETA\NET4 which I think is correct for your latest DLL. This line private Offset<SimConnect6DOF> cameraSetRelative = new Offset<SimConnect6DOF>("camera", 0x86A0, true); is giving me a compile error: A first chance exception of type 'System.NullReferenceException' occurred in FSUIPCClient.dll Additional information: Object reference not set to an instance of an object.

Paul, After I unzip your DLL what folder do I put it in? I've been away from this for a while and don't recall what folder your DLL should be in? Thanks...

Wow, thanks for the code Paul...I'll give it a try...

Hi Paul, Pete provided me with the offsets to test moving the cockpit camera via the SimConnect function SimConnect_CameraSetRelative6DOF(). Pete built me a special beta version of FSUIPC for me to test with. The information he provided: Offsets 86A0, 86A4, 86A8, 86AC, 86B0 and 86B4 (ie 6 consecutive 32-bit values) should be written with the 6 float parameters for SimConnect_CameraSetRelative6DOF. The action is triggered by a write to 86A0, so either write that parameter last, or, better, write all 24 bytes as one structure, in one Write. Paul, can you give me an example of how the c# syntax should be written to make this call after loading the 6 values for the XYZ and PBH arguments? I'm going to load up some known values I took from inside an F-18 fighter and then I will set up the DOF() call via FSUIPC and make the call and observe if the camera position does indeed change (and report this back to Pete). Thanks...

Email sent...(My Win7 system crashed and I just now got it re-built thus the delay)...

OK...I just thought I'd ask. I'm writing a camera view app and SimConnect has a call that allows me to update the camera changes in real time as I make changes with an app, so I'm going to have to use SimConnect for this project. Your FSUIPC .DLL worked so well with my other project I was hoping you did one for SimConnect :smile: Thanks...

Hi Paul I wanted to ask if you have done a .DLL wrapper for SimConnect? Thanks...

Thanks Pete...that looks like what is needed to dynamically update the x y z p b h values in real time...and then once set, write those values to the appropriate aircraft.cfg file. Update: I've had a detailed look at the aircraft.cfg file structure and it's just like a Windows .ini file so I have a C# Class to read and write to ini files already. So, that part is now solved as far as how to do it.

So that web page provides some excellent information on the cockpit cameras, how to create them and how to edit existing ones. I have to edit the specific aircraft config file. From a development point of view, I'm wondering how a camera app edits the aircraft config file and shows the effect of the changes in real time? In other words, is this done in memory until finished and then the .cfg file data is written to the disk -- or -- are the changes done to the .cfg file and they have to be written to the disk and the aircraft.cfg file re-loaded to see the changes? I'm trying to find out what the edit/load/refresh cycle is for aircraft .cfg file. Pete - I'm wondering if I can do this camera app using FSUIPC or if I need to make use of SimConnect?

Thank you very much...I had not seen that yet...

I'd like to write my own camera utility to create, edit and delete my own camera views for FSX. My development environment is VS 2013 C# and I already have a registered copy of FSUIPC and also Paul's FSUIPC Client .DLL. So I can already 'talk' to FSX. I'm wondering if there are any tutorials that sort of go over the steps needed to create your own camera views? My assumptions at this point are: 1. Camera views are contained inside a specific aircraft's .cfg file? 2. To create a new camera view, requires creating a new camera entry in the aircraft.cfg file ([CameraDefinition.2] section for example)? 3. I'm not sure how to activate a camera view via FSUIPC? I assume I would need to send a camera command to FSX? 4. So my camera app would mainly have to read and write to the aircraft.cfg file (in the camera section) and then just select which camera view to switch to? 5. What is the difference between the camera.cfg file and an aircraft.cfg file (the camera settings in each one I mean)? Why are there two .cfg files to define and control cameras? Thanks for any pointers and help in where to read more about how to do this project.