I see now. Ok, so I was getting close at 454.

 

Thanks for letting me take up so much space with my log and I REALLY appreciate you taking the time to explain things to me.

 

You have now made my simming a little easier for me Tom.

 

Best regards.

 

Jack

No problem, happy simming!

Tom, I'm still getting a VAS reading with letters in it which means HEX but I know for absolutely sure it's not checked.

The VAS goes back and forth with Hex and all numbers.

How can this be?

 

Also, I just installed UK2000 EGNX, in setup I disabled a lot of stuff and starting off my VAS is 1552396!  Isn't that kind of low?

I disabled ALL my ES stuff too.

 

And I'm getting stutters even though I have a solid 30 FPS.  Using A2A's 182.

 

PC specs:

 

Jetline Hellfire GT2 PC

Win 7 Pro 64

CM Storm Scout II Advanced case

ASRock Fatal1ty Z97 Pro, Intel LGA 1150 mobo

i7 4790 Quad Core 4.66 GHz

Corsair Hydro H80i Liquid Cooling

8 GB Trident X DDR3 SDRAM 2133 MHz

500 GB Samsung 840 EVO SSD

500 GB Samsung 840 EVO SSD

 

4 GB Nvidia GeForce GTX 980 - Driver GeForce 344.65 WHQL

NV Inspector version - 1.9.6.5

 

Creative Sound Blaster Z SBX 

Integrated High Speed Network 10/100/1000

802.11n WiFi card

750 Watt Corsair RM Power Supply

20x DVD/CD Burner

FSX Gold

Saitek PZ44 Yoke & throttle - Yoke driver

Saitek PZ35 Pro Flight Rudder Pedals

Samsung S27A550H Monitor

Buttkicker Gamer 2

 

Track IR 5 S/N 245800

Driver 5.2.200 DO NOT UPDATE!!

 

EZCA version: 1.16 - DO NOT UPDATE!!

 

ORBX

Trees HD

England regional

Scotland regional

Wales regional

Sumburgh Scotland

Ireland regional

Northern Ireland regional

Australia regional

FTX Global

Northern California

Pacific Northwest

Central Rocky Mountains

Northern Rocky Mountains

Pacific Fjords

Sedona Arizona - KSEZ

Jackson Hole - KJAC

EGPB - Sumburgh, Lerwick, Scotland

EGFF - Cardiff, Wales

Yellowstone - KWYS

Southern Alaska

NSTU - Pago Pago

11S - Seiku - Pacific Northwest

New Zealand South Island

PAEN - Kenai Southern Alaska

PAHO - Homer Alaska - Southern Alaska

PAJN - Juneau Alaska - Southern Alaska

PAGS - Gustavus Alaska - Southern Alaska

PAYA - Yakutat - Southern Alaska

CZST - Stewart - Pacific Fjords

PAKT - Ketchikan - Pacific Fjords

CYBD - Bella Coola - Pacific Fjords

KORS - Orcas Island - Pacific Northwest

 

Tongass Fjords

PASI - Sitka AK

PAFE - Kake AK

PAPG - Petersburg AK

PAKW - Klawock AK

PAWG - Wrangell AK

CZST - Stewart Canada

CBM5 - Telegraph Creek (Not in GTN)

CBW4 - Bob Quinn lake

CAB5 - Bronson Creek (Not in GTN)

CAB6 - Scud River Mine (Not in GTN)

Yehiniko Lake - (Not in GTN)

Cirque, Galore Creek - (Not in GTN)

Portal, Galore Creek

Many seaplane bases, see page 34

See also, Where do the ships go?

 

ORBX airports FREE

7WA3 - West Wind NOT in GTN

2S1 - Vashon Island also WA69 on Vashon Island

2S1 is in GTN but WA69 is not.

CEJ4 - Claresholm, Alberta

CEN4 - High River Regional, Alberta

KHQM - Bowerman - Pacific Northwest

 

PDX city, just the city of Portland.

 

FSUIPC latest version 24 October 2015 not using registered version

 

Active Sky Next 

 

FS DreamTeam:

GSX

 

Earth Simulations:

Isle Of Man 

Guernsey 

 

Crazy Creatives:

L41 Marble Canyon

 

Flightbeam:

KSFO - San Francisco

KIAD - Dulles

 

Flight1:

All UTX's

UT2

GTN750 GPS

EZCA version 

Scenery Tech:

Indo-Pacific landclass

North America

Europe

 

UK 2000:

EGKK - Gatwick v 3.3 Extreme

EGNX - East Midlands Extreme

 

Fly Tampa:

KTPA - Tampa

KBOS - Boston

OMDB - Dubai

St. Maarten TNCM & TFFJ, SABA

Grenadines - 

TVSB, TVSM, TVSC, TVSU, TGPZ  

LOWW - Vienna

 

Aerosoft:

PFPX

TOPCAT

Approaching Innsbruck - LOWI

Nice - LFMN

 

Taxi 2 Gate:

TLPC - St. Lucia - George F.L. Charles

 

Aircraft:

 

Majestic

Dash 8 Q400

Training videos for Dash 8

 

Aerosoft:

Twin Otter

 

Carenado:

Cessna C337H Skymaster

C208B Grand Caravan EX HD

 

Alabeo:

Cessna Titan C404

Piper Sport Cruz

 

RealAir:

Duke Turbine V2

Lancair V2

 

A2A:

172

182

Cherokee

Comanche

Piper Cub

P-51 Mustang military

 

PMDG:

737-NGX

600/700 add on planes

AOA FlightWork video lessons for 737-NGX

 

Lotus Simulations:

L-39 Albatross 

 

 

starting off my VAS is 1552396! Isn't that kind of low?

 

Jack, that is an entirely reasonable value. This is VAS memory remaining, it is equivalent to 1.55 GB which is more than one fourth of your total 4 GB VAS available.

 

A hexadecimal number has values from 0-9 then A-F (sixteen values... hence hexadecimal) so you can't tell if it's decimal or hex if there's no alpha chars but if there are alpha chars then it is probably hex.  You can also use Process Explorer (see section on VAS in 777 Introduction if you have that product) and it will provide amount used instead of remaining.

Thanks Dan for the reassurance.

I don't really want to run another app.

I have discovered though through trial and error that when I have the FSUIPC VAS monitoring on in full screen I get a HUGE amount of stutters.

So I shut it off mid-flight and the stutters disappeared but I kept it logging to a file.

I have the freeware version and I also have the payware version I never bothered to register because I use Saitek's stuff and I find FSUIPC impossible to program the Mode 1-2-3 button.

But still, why do I get the letters mixed in with numbers then it goes to all numbers.  For example, it'll read something like this, 1234B567 why when hex is NOT checked?

FSUIPC bug?

 

Thanks for your help Major. Sir.

I spent 8 in the AF working avionics on F-111's in Heyford and Mt. Home.

Got out as an E5 and turned down E6.

Always good to speak to a fellow Air Force vet!

 

 

I spent 8 in the AF working avionics on F-111's in Heyford and Mt. Home.
Got out as an E5 and turned down E6.
Always good to speak to a fellow Air Force vet!

 

I was at Upper Heyford numerous times during the late 70's, primarily to visit the big comm organization nearby at RAF Croughton. I was lucky enough to jump from E5 to O1 with USAF sponsoring my BSEE, very lucky. Mt Home is a different story, working on the flight line in Idaho in winter is tough.

 

Set FSUIPC to display on the title bar, this has no impact on frame rate and stutters. I never use a log file, I'd always forget to delete them and they can get big.

Jack none of the VAS amounts indicated in the log file you posted, has alphas or give any indication they are hexadecimal, but if you still are seeing them even with the Hex button not checked then I think you need to post this over at Peter Dowson's support forum. He should be able to help at this point.

 

http://www.schiratti.com/dowson.html

I was at Upper Heyford numerous times during the late 70's, primarily to visit the big comm organization nearby at RAF Croughton. I was lucky enough to jump from E5 to O1 with USAF sponsoring my BSEE, very lucky. Mt Home is a different story, working on the flight line in Idaho in winter is tough.

 

Set FSUIPC to display on the title bar, this has no impact on frame rate and stutters. I never use a log file, I'd always forget to delete them and they can get big.

Had many a Newcastle Ale at Croughton!

 

If I set it to display in the title bar then don't I have to fly in windowed mode?

I like full screen.

Jack none of the VAS amounts indicated in the log file you posted, has alphas or give any indication they are hexadecimal, but if you still are seeing them even with the Hex button not checked then I think you need to post this over at Peter Dowson's support forum. He should be able to help at this point.

 

http://www.schiratti.com/dowson.html

Good idea!

I'll do it as soon as I am able.

 

 

Good idea!

I'll do it as soon as I am able.

 

Another option is to use a VAS monitor available here in the library

 

http://library.avsim.net/search.php?SearchTerm=vas+monitor&CatID=root&Go=Search

 

Or this one from a Twitch user pawkbun for ProjectFly. I like this one as it also includes a landing rate tool.

 

http://pawkbun.co.uk/

 

 

If I set it to display in the title bar then don't I have to fly in windowed mode?
I like full screen.

 

Yeah there is that, I don't use full window because I need my taskbar to access ASN, PFPX and Navigraph Charts during the flight as well as browse Wikipedia on long flights.  Here is my settings for VAS display on title bar, simple:

 

If I set it to display in the title bar then don't I have to fly in windowed mode?

 

I like full screen.

 

You can select a FS Window which will work in full screen, but my experience it will affect performance. (Cause stutters)

Yeah there is that, I don't use full window because I need my taskbar to access ASN, PFPX and Navigraph Charts during the flight as well as browse Wikipedia on long flights.  Here is my settings for VAS display on title bar, simple:

 

That's what I use my iMac for and the iPad.

You can select a FS Window which will work in full screen, but my experience it will affect performance. (Cause stutters)

I discovered this today in a BIG way!  LOL!!

Ok, I have been testing all day.

UK2000's EGNX to UK2000's EGKK.

In the A2A 182.

ASN on

Track IR

GTN750

Saitek yoke, pedals, and quad and TPM.

 

I have been gradually adding things in the scenery library and see very little difference.  If anything I see VAS increase in all three logs as I went on.

 

But in the last two logs I came across this several times scattered throughout the VAS readings.

 

"G3D bad pointer trapped and crash prevented".

 

What does that mean?  I don't have a clue.

 

Thanks.

 

 

"G3D bad pointer trapped and crash prevented".

 

Welcome to programming. I encourage you to stay in the light and not go down the dark tunnel, lest you go too far and let it consume you.

 

[Disclaimer: I'm trying to keep this light / high level, so I might use terms loosely...]

 

A pointer is essentially a reference to a memory location. If you don't program properly, you can end up pointing code at a location that contains nothing (uninitialized pointer), which can cause programs to misbehave. Basically, something related to G3D pointed to a bad location and something stopped it (somehow).

Welcome to programming. I encourage you to stay in the light and not go down the dark tunnel, lest you go too far and let it consume you.

 

[Disclaimer: I'm trying to keep this light / high level, so I might use terms loosely...]

 

A pointer is essentially a reference to a memory location. If you don't program properly, you can end up pointing code at a location that contains nothing (uninitialized pointer), which can cause programs to misbehave. Basically, something related to G3D pointed to a bad location and something stopped it (somehow).

Kyle, um, what? Huh? You lost me man.

No, I don't have a clue about programming. Wish I did.

My memory location is right here in Georgia/sarc

Seriously, I was looking for something more specific like if I had something wrong.

So while I was awaiting a reply I googled it and found many references on Pete Dowson's FSUIPC site.

So I downloaded his latest version and registered it and am testing it now.

I'm good at real-world avionics but don't have a clue about programming. I did teach myself BASIC, way, way, WAY, WAAAAY back in the 1980's! LOL

 

 

Kyle, um, what? Huh? You lost me man.

 

Yeah. That's a tough lesson when it comes to programming. At least it was for me...finally clicked a while later.

 

Not much you can do about it, though. Bad pointers are all the programmers. So, in that vein the only thing you can do 'personally' is report a bug to someone, but you'd need to track it down a little bit more to figure out who to send the report to.