Jump to content

Wolfe Blackburn

Resident
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Wolfe Blackburn

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank y'all for your suggestions. Things I've tried so far which did not have an impact at all: Setting folder (Firestorm's local and roaming AppData) and process exlusions in Windows Defender Turning off all the bells and whistles in /System Properties/Advanced/Performance Texture memory setting in Firestorm is maxed out at 512 MByte Further differences I observed: Under Windows 10 I have an average of about 40% CPU load on all 4 cores - under Windows 7 only 2 cores are under load (40-50%). GPU load runs about 50-60% under both OS (no real difference to obser
  2. I am in the process of finally migrating from Windows 7 to Windows 10. I have a dual boot installation. So I can directly compare performance under Windows 7 and Windows 10 on one and the same machine. The problem is: under Windows 10 the fps is about 30-40% of what I get under Windows 7. My system is a AMD FX-4350 with 16 GByte of ram and an AMD HD-7750 graphics board. Both Windows 7 and Windows 10 have the current graphics drivers from AMD installed. The problem is not viewer dependent; it happenes with the LL viewer as well as Firestorm. Graphics settings in the view
  3. Lucia Nightfire was so nice to come over to my place yesterday evening to test that old teleporter which I have. To my surprise, she told me that her camera does stay behind when she uses my tp! She suggested that I try again using the LL viewer (I only use FS) to make sure that it's not one of the many switches FS has in its move/view preferences that make my camera follow the tp. I will do that. So the mystery remains. Because the camera does not follow me when I use my own tp script. I'll keep y'all updated in this thread.
  4. Yes I studied Dora Gustafson's scripts. Setting the camera to the target position only works when camera control has been released prior to the teleport - and then you don't have the problem in the first place. Yeah I know, both warppos and jumppos are outdated. I used them temporarily to see if it would make any difference with the problem of the camera staying behind. llSetRegionPos (followed by a final llSetPos for a finishing touch) sure is the way to go. --- I did some more testing with a vehicle - really making sure that I did use my camera control before sitting on it.
  5. OK ... if that is expected behavior, then I have 3 more questions to help me understand what is going on: Why do I not have to hit ESC when sitting on a (physical) vehicle? As soon as I sit, the camera goes in position behind and above the vehicle. This works no matter if I am wearing a camera hud or not (I tried 2 camera huds, my own and a commercial product, makes no difference). Why do I not have to hit ESC before sitting on the teleporter when I do NOT wear my camera hud? What might the scripter of my old 2008 teleporter have done to overcome the camera problem? If I use
  6. I am in the process of creating a teleporter for local use on a sim. I have a 10 year old commercial product (the creator left the grid so I can't ask him) which works perfectly but does not have access control. So I decided to make one myself. Anyway, this is how the original product (and my current work) works: Avatar touches a prim (can be linked with other object, like building). Script in prim checks if avatar is authorized and then rezzes a prim to sit on (the beamer). The beamer transports avatar to destination and then self destructs. So far, so good. All this works nicely. I
×
×
  • Create New...