Thralni

This is great news, however clicking the link in the original email still downloads a file that has "sp2" in the name, rather than "sp3"? *

I'm aware that Aeroplane Heaven did the modeling. Feelthere should definitely ask them to optimize the model a lot 🙂 I do hope that a next SP will deal with these issues. I suppose we can only wait and see. I appreciate your response, but it'd been great if you hadn't been the only one to comment here. Was sort of hoping somebody from Feelthere would give an idea as to how they might deal with this issue, either themselves or AH.

Thanks for your reply Riky. It strikes me as strange that a v4 model causes such a high VRAM usage. is this something specific to aircraft? Because while I noticed that v4 scenery doe snot seem to perform quite as well as v5 scenery, it doesn't lead to such high VRAM usage. It seems to me that it must then be a combination of v4 models and very poor optimization. Like I said before, these aircraft use four texture maps to cover the fuselage, have some special maps dedicated entirely to the pilots... and some of these are almost half empty! Surely they could have merged these textures? This is a little ridiculous. They really need to address this... FYI, this is not just a problem in v5. In v4, VRAM usage doesn't lead to immediate issues because of the differences between DX11 and DX12, but that doesn't mean that running out of VRAM in DX11 is 'okay'. Far from it: it will also lead to bad performance. So, for the sake of both the v4 and v5 users, this plane needs to be optimized rigorously.

Hello, I posted about this on Avsim before and there it was made clear to me that my issue is one that is inherent to the Embraer v3 series and not just on my end. So I'm posting here now to see why that is happening and what can be done about it. Note that I am on P3Dv5 HF1. Specifically, the Emb v3 appears to have crazy high VRAM usage. So much so that it becomes pointless for me to even fly it. See below. I have done a survey of VRAM usage on my computer. I started out with the default flight, set the location to VTBS (Bangkok), chose the default F22. Because it's tjhe default flight, time and day are set the same every time. I then loaded the flight, waited a couple minutes for things to settle, made sure to look all around in both interior and exterior view so as to load all textures in view, and then I noted VRAM usage. I then quite P3D, restarted it, and moved on to the next aircraft. Here are the results: Default F22: 3.2Gb PMDG 738NGXu: 3.8Gb PMDG 744: 3.8Gb Aerosoft CRJ: 3.6Gb Feelthere EMB-190 v3: 5.1Gb FSLabs A320: 3.6Gb My texture resolution setting is set to 1024. As you can see, the Feelthere Emb-190 clocks in at a VRAM usage that is 1.3Gb higher than any other addon airplane I tested. This includes aircraft with PBR VCs, such as the Aerosoft CRJ. What on earth does the Emb-190 have that requires it so much more VRAM usage? And note that I already put my textures on 1024, thus 4k textures should not be the issue per se. It seems to me that the model must be grossly unoptimized, possibly by not combining texture files where possible. For exmaple, I see THREE textures that relate to the pilot, all at 4k. Isn't this a huge waste of space...? Also, I noticed that there is a virtual cabin that cannot be turned off. From what I understand, the model and texturing was done by Aeroplane Heaven, but nevertheless: does Feelthere have any plans to tackle the high VRAM usage, or at least ask AH to do something about this? I just ain't really willing to push my settings lower just to be able to fly this one addon plane, and frankly I don't think I should need to when both computationally more intensive or graphically just as convincing addons seem to have little issue. Best, Benjamin

Aaaah, okay. Sorry, I misunderstood you then. But what I meant with setting the throttles in FSX is that I assigned the Saitek levers to the throttle commands via FSX's controls window instead of via FSUIPC.

Ah, see? That's why I posted, because I didn't even see that there were multiple options for setting the throttle axis. I thought that Throttle1_set and Throttle2_set were the only ones... Probably overlooked the other ones. As such, I didn't calibrate them, because I couldn't. If I could, I would have certainly bothered to calibrate them, but In the calibration window none of the values changed when moving the throttles. I'll try setting the throttles using the AXIS_Throttle1/2_set assignments and see what happens. As for why not using the FSX default assignments instead, isn't that obvious? It would defeat the entire purpose of using FSUIPC... The point is that every aircraft is different and using FSUIPC's profiles I do not have to go into the FSX controls window to change it for every other airplane I fly. UPDATE: Edited the assignments using the Axis_throttle1/2_set, and it work brilliantly now. Thanks!

Hello Pete and others, I know, again a thread about the Wilco Airbus and getting the Saitek TQ to work with it. But yeah, I have a problem that won't go away: the throttle is responsive, but it doesn't do at all what it is being told. Here are things I did: - To test if it works at all, I assigned engine 1 and 2 to the Saitek throttle levers within FSX. That worked: the Wilco throttle levers were responsive and worked correctly. - I went back into FSUIPC and assigned the throttle axes of the Saitek yoke using the "send to FS as normal axis" option. - In the joystick calibration window, I made sure that "no reverse zone" was ticked. - In the FSUIPC4.ini file, I made sure that the joystick calibration section of this particular profile (called wilco A330) has the "UseAxisControlsForNRZ=Yes" parameter. After all this, it still doesn't work. What I get is this: When I move my Saitek throttle levers, the throttle levers in the Wilco do not move. Instead, the thrust ramps up for a bit, accompanied by a thrust reverser sound, but it quickly cuts out and returns to idle. So, there is a response, but it's completely wrong. This is the relevant part of the FSUIPC4.ini file: [Profile.Wilco A330] 1=Feelthere A330-200 GE Airbus Air Greenland [buttons.Wilco A330] 0=R2,21,C65966,0 1=U2,21,C65967,0 2=R2,22,C65971,0 3=U2,22,C65972,0 [Axes.Wilco A330] 0=0X,256,F,65763,0,0,0 1=0Y,256,F,65694,0,0,0 2=1Z,256,F,23,0,0,0 3=2Z,256,D,22,0,0,0 4=2U,256,F,65820,0,0,0 5=2V,256,F,65821,0,0,0 [JoystickCalibration.Wilco A330] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=Yes FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Aileron=-16384,0,1933,16254 Elevator=-16384,-512,512,16320 Throttle1=-16384,-512,512,16383/32 Throttle2=-16384,-512,512,16383/32 Throttle3=-16258,-512,512,16383/32 Throttle4=-16384,-512,512,16383/32 Spoilers=-16384,16383/16 Flaps=-16384,16383 For your information: - I use FSX + Acceleration - This is FSUIPC 4.703 - The product is Wilco Airbus Volume 2, patched to the latest version, but this is NOT the evolution version that was released some time ago. - All other addon planes I have work great. - Most of the assignments are from within FSUIPC, because of the various needs of my addon aircraft (Airbus using control sticks, others using yokes etc etc) I hope somebody can help. For as far as I can see I have done everything that I had to do (use "send to FS as normal axis", tick the "no reverser zone" box and put in the "UseAxisControlsForNRZ=Yes". Maybe I missed something, in which cause any one of you can highlight it for me.

The log says I have version 3.98a. But surely, if I get documentation with this version that mentions the GUID check, than this version should be able to do that? or is the documentation newer than the module? I'll try to 3,989m, thanks! See if that works.

For some reason, no GUIDs appear in [Joynames]. I have tried reinstalling FSUIPC, deconnecting, reconnecting the hardware but to no avail. I'm using FS2004 with FSUIPC 3.98a in Windows 7 64bit. Any reason the GUIDs won't appear?

Never mind, problem solved. After I jumped once again into the axis settings and joystick calibration of FSUIPC, I finally started understanding how the tabs work together. So, what I did: 1) I disabled the FS axis assignment I had made. 2) I went into FSUIPC, and assigned the relevant lever to flaps axis. 3) I went to the flaps calibration page in the calibration tab, and looked if all was okay 4) tested it out with a variety of default and addon aircraft, and to my satisfaction, everything worked as it should. 5) Went back into FSUIPC, and configrued the spoilers lever in the same way 6) Voila, everything works fine. Thanks for the help. You prompted me to go back into FSUIPC and try to fully comprehend what it is I'm seeing.

Thanks for the reply Pete. A number of things: First things first. The second post I made was about the flaps axis in FS itself, but it is here where my current problem started. I eventually found that there is a flaps axis, because I hadn't seen it before (I must be blind - I searched the axis assignment screen at least four times). I then assigned the lever I wished to use with it in FS, but then the current problem started: the parabolic way of flap movement (middle is fully retracted, fully extended at both ends) So, it boils down to correct calibration? I have done that multiple times via the FS way, making sure that 0% is indeed 0% and 100% is indeed 100%, so that I use the full range of the lever, just like the 4 throttle levers I have. However, the 4 throttle levers work absolutely fine (and the spoiler lever too, by the way). 0% is engines idle, 100% is full thrust. The flaps lever, however, does not work. I mean, it works, but it works in a parabolic way, as I explained. On the middle it reads flaps 0 and at both ends it reads flaps full. this is also what is beyond me. I have done the calibration - and I think I did it correctly - at least three times, but it doesn't work as it should. I guess I'll try to calibrate again. You also speak of the user manual, but what manual exactly do you mean? The FS2004 help files, the FSUIPC manual or the Saitek manual? Because the Saitek manual does not explain these things (and why should it?) and I did look at the FSUIPC manual (otherwise I probably would have never thought of the possibility of assigning a flap to an axis so easily). I'll look at the calibration steps if the FSUIPC manual, though. See if that can help me out. By the way, the second post started out with edit, simply because I had edited that post... I posted, then came to the conclusion that what was in the post was wrong, and edited it. Then I did a second edit. The reason I edited was that I thought that I had understand what was going wrong. However, I didn't, so I edited the post.

EDIT: I thought I had figured out, but I still have absolutely no idea what I'm doing. I did get something woprking by choosing the relevant lever as the Flap axis in the FS assignments windows, but it doesn't behave at all like I want it too. What the hell should I be doing... I really have no understanding of all of this... For some reason, the throttle's 50% position is what is seen as Flaps 0, while FSUIPC clearly seems to say that Flaps 0 is at -16383, which is the way it should be (and Flaps 8 is at 16384, which is also why it should be). I just can't figure out why in the sim itself, what sould be flaps 4 is seen as flaps 0, and both flaps 0 and flaps 8 are seen as flaps 8...

Hello, Since I got Saitek throttle quadrants today, I'm very busy turning it all into something productive. Part of this is making a flap lever. I have found the instructions in FSUIPC's manual, but I have a very silly problem: when I move the relevant lever, the numbers do not change in the Flaps box of page 6 of the joystick calibration tab. Now, i suppose I should be setting up the lever I want for the flaps so that FSUIPC knows it is this specific lever that I want to use for the flaps. However, I have no idea where to even start looking. This is my very first time of seriously using FSUIPC. Could somebody help me out? So in short, the lever I want to use for flaps does not generate a response in the Flaps box of page 6 of the joystick calibration tab (numbers do not change). What could/should I do to make that happen?

Aaah, I see. Thanks for the clarification!

Okay, thanks, that's what I wanted to know :-) By the way, it appeared I had completely misunderstood what the FSC( manual tried to tell me. At the very end, in the appendix, I came across long explanation of how to configure shared folders, and thus made the folders available to my laptop. After I had followed up that explanation, I found the necessary folders in the database manager, and it is now happily scanning the FS2004 directory for scenery files. It seems the problem is solved. (In all honesty, I never in my life tried any networking and file sharing, and all the file sharing that I did too was with Mac OS X, not Windows) But, it's good to know that WideFS actually connects :-)

Hey guys, I recently bought WideFS and tried to connect my laptop (WindowsXP) to my FS machine (Windows 7 64 bit). Now, it seems that it actually is connected. WideFS says "connected" in the manu bar, and FS9, when ina flight, says "one client connected" or something similar. So, it seems there is a connection. However, is there anything that visually changes in the client (except the notification in the menu bar) upon connection? because all I see is a grey screen. Is that what I'm supposed to see? The client screen doesn't fill up with anything, is that correct? The reaosn I'm asking is that I want to have FSCommander 9 link to FS9 via WideFS. In the manual it says that updating the airports in FSC9 is oh so very easy by simply connecting the computer on which FSC9 is installed via WideFS to the FS9 computer. Then you should run FSC9's database manager and select the drive on which FS9 is installed in a drop-down menu. However, I cna do no such thing. My first thought is that there might be something wrong with the connection (hence my question). My second thought was that the networks drive has exactly the same name and drive ketter as the drives on my laptop and the databse manager might find that a problem. So, back to my question: can anybody tell me what the visual changes are in thw WideClient? here are some possibly relevant logs: ********* FSUIPC, Version 3.98a by Pete Dowson ********* Running on Windows Version 5.1 Build 2600 Service Pack 2 Verifying Certificate for "C:\Flight Simulator 9\MODULES\FSUIPC.dll" now ... SUCCESS! Signature verifies okay! Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="Benjamin van Soldt" User Addr="B.J.van.Soldt@inter.nl.net" FSUIPC Key is provided WideFS Key is provided Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=401C360D[401C360D] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=255 1934 System time = 16/11/2010 12:06:31 1934 C:\Flight Simulator 9\ 1934 System time = 16/11/2010 12:06:31, FS2004 time = 12:00:00 (00:00Z) 18627 FLIGHTS\OTHER\FLTSIM.flt 18642 AIRCRAFT\c172\Cessna172SP.air 18658 Aircraft="Cessna Skyhawk 172SP" 23884 Advanced Weather Interface Enabled 42432 \\BIMACWIN\Users\Benjamin van Soldt\Documents\Flight Simulator Files\UI generated flight.flt 42682 Clear All Weather requested: external weather discarded 51231 Traffic File #371 = "scenery\world\scenery\traffic_214_woa_pakistan international airlines_wi07" 51902 Traffic File #65 = "scenery\world\scenery\traffic_000_woa_airblue_su08" 51917 Traffic File #407 = "scenery\world\scenery\traffic_pai" 51980 Traffic File #137 = "scenery\world\scenery\traffic_000_woa_emirates_su09" 52011 Traffic File #299 = "scenery\world\scenery\traffic_000_woa_ultimate ga citation 550_su06" 52276 Traffic File #387 = "scenery\world\scenery\traffic_254_woa_ultimate ga cessna 402_su06" 392811 System time = 16/11/2010 12:13:02, FS2004 time = 11:03:56 (07:03Z) 392811 *** FSUIPC log file being closed Memory managed: 0 Allocs, 7221 Freed ********* FSUIPC Log file closed *********** ********* WideServer.DLL Log [version 6.78] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 16/11/10, Time 12:06:32.437: Server name is BIMACWIN 53930 Initialising TCP/IP server 53930 Initialising IPX/SPX server 53930 IPX/SPX socket() failed [Error=10044] Socket type not supported 53930 Failed to start IPX/SPX Server 53930 Initialising UDP/IP server 54366 Broadcasting service every 1000 mSecs 58719 Incoming connection Accepted ok (skt=532) TCP 58719 Connected to computer "MACBOOKPROWINXP" running WideClient version 6.780 (skt=532) TCP 396024 Close signalled to clients 397116 Closing down now ... Memory managed: Offset records: 15 alloc, 15 free Read buffer usage: 149 alloc, 149 free, max in session: 1 Write buffer usage: 14419 alloc, 14419 free, max in session: 1 Throughput maximum achieved: 2 frames/sec, 203 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 17 bytes/sec Average receive rate from "MACBOOKPROWINXP": 0 frames/sec, 18 bytes/sec ********* Log file closed ********* ********* WideClient Log [version 6.78] Class=FS98MAIN ********* Date (dmy): 16/11/10, Time 12:06:37.828: Client name is MACBOOKPROWINXP 282 Attempting to connect now 282 Trying TCP/IP host "BIMACWIN" port 8002 ... 282 ... Okay, IP Address = 10.0.1.3 21266 Error on client pre-Connection Select() [Error=10060] Connection timed out 21266 Ready to try connection again 22282 Attempting to connect now 53203 Connection made okay! 385125 Received shutdown offset code = ADBC 385125 FS closing down (param=ADBC), disconnecting 385125 ********* Interim performance summary ********* 385125 Total time connected so far = 330 seconds 385125 Reception maximum so far: 2 frames/sec, 117 bytes/sec 385125 Reception average whilst connected so far: 1 frames/sec, 41 bytes/sec 385125 Transmission maximum so far: 0 frames/sec, 20 bytes/sec 385125 Transmission average whilst connected so far: 0 frames/sec, 19 bytes/sec 385125 Max receive buffer = 368, Max send depth = 1, Send frames lost = 0 385125 *********************************************** 385235 Received shutdown offset code = ADBC 388578 ****** End of session performance summary ****** 388578 Total time connected = 330 seconds 388578 Reception maximum: 2 frames/sec, 117 bytes/sec 388578 Reception average whilst connected: 1 frames/sec, 41 bytes/sec 388578 Transmission maximum: 0 frames/sec, 20 bytes/sec 388578 Transmission average whilst connected: 0 frames/sec, 19 bytes/sec 388578 Max receive buffer = 368, Max send depth = 1, Send frames lost = 0 388578 ********* Log file closed (Buffers: MaxUsed 2, Alloc 610 Freed 610 Refused 0) *********